Continuous integration
If integration and integration tests are important, then code should be integrated as often as possible – preferably, several times a day. This will prevent your team from working with different copies locally and encourages them to work alongside each other. Any integration problems will also become immediately visible. GitLab CI was created for this reason, and was introduced in Chapter 1, Introducing the GitLab Architecture.
One of the key reasons CI is used is to prevent integration problems, which can occur if developers work on their own for too long. Imagine the phenomenon of integration hell, where at the last minute before release, a developer merges a big chunk of code that then introduces conflicts.
Continuous ...
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