11
ENABLE AND PRACTICE CONTINUOUS INTEGRATION
In the previous chapter, we created automated testing practices to ensure that developers get fast feedback on the quality of their work. This becomes even more important as we increase the number of developers and the number of branches they work on in version control.
The ability to “branch” in version control systems was created primarily to enable developers to work on different parts of the software system in parallel without the risk of individual developers checking in changes that could destabilize or introduce errors into trunk (sometimes also called master or mainline).*
However, the longer developers are allowed to work in their branches in isolation, the more difficult it becomes to integrate ...
Get The DevOps Handbook, 2nd Edition 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.
