Modern C++ Programming with Test-Driven Development

11.7 Continuous Integration

How many times in your career have you heard the phrase “It worked on ​my​ machine?” Or perhaps you have uttered it yourself? Until your code is integrated with the rest of the production code and passes all tests running on an approved machine (one with an environment similar to production), you don’t really know that it works. (You still don’t ​really​ know that it works, of course, until it’s sitting in front of the customer.)

The job of a ​ continuous integration​ (CI) server is to monitor your source repository and kick off a consistent build process when a commit occurs. Once the build completes, the CI server notifies any interested parties and retains build output for future reference.

Your build script should ...