3.4. Summary
The point of Continuous Integration is to reduce the risks posed by integrating the work of many developers and to keep as many people working in parallel as possible. To that end, a CI process is designed to build software as often as possible. This is usually done by setting up a Continuous Integration server that builds a project automatically, without human intervention, preferably every time a change is committed.
This process provides testers with continuously updated versions of the software to test, and increases developer confidence in the integrity of the latest version of the source code, which makes it easier for them to stay up-to-date, and reduces the risk of integrating each individual change with the rest of the project.
The only way to gain full benefit from a CI process is if every developer takes it as a personal responsibility to keep the build from breaking so that other members of the team can keep working and integrating their changes as soon as they are completed.
Get Code Leader: Using People, Tools, and Processes to Build Successful Software now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
