What Is Continuous Integration?
In software engineering, the name “continuous integration” only makes sense in the context of history. Before the implementation of CI, software teams used version control to keep track of code updates, and different developers would add a feature or fix a bug on the separate code branches. At some point, the code was merged, built, and (hopefully) tested. The frequency of this merge varied from “when your code is ready, merge it” to regularly scheduled merges, maybe weekly or every other week. This merge phase was called integration because the code is being integrated together.
With this sort of version control, code conflicts happened often. Therefore, some teams had dedicated people to do the merge and debug ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access