Continuous Integration - AMABK/engineering-playbook GitHub Wiki

The basics are:

• We have unit tests that each developer runs on their own machine.
• When they commit their code to git, the tests are run again, "integrated" with code from other developers.

This helps ensure there's nothing specific to the developer's machine making the tests pass. The code in version control needs to run cleanly in production later so before the code is allowed to be deployed to production, it is run on a CI server or service.

When a build fails, send alerts in Slack and/or other platforms. Click the alert and we see a backtrace that gives us a hint of how to "fix the build." When we write the fix and commit to version control again, we'll get a "passing build" alert in Slack and via email. Click the alert and we see the passing build.

Green is good.

For continuous integration, we use CircleCI and Jenkins (for some of our Apprenticeship product services).

CI test runs are triggered when we push to Github and can be seen as part of the status checks of pull requests. We also use CodeClimate to help us follow our style guide and keep review comments focused on improving the code quality.