Keeping The Build Unbroken

Continuous Integration only works if you integrate. The constant build should always stay intact. A broken build is a Stop the Presses event. Sirens are going off. The mantra of the team must be The Build Never Breaks. At this point, the essential task is fixing it and getting the build working. In a Continuous Integration environment, you should always have a successful Integration build stay fell for a long. A good team should have many correct builds a day. Bad builds do occur from time to time but should be fixed. Software projects involve many files that must be orchestrated to build a product. Keeping track of these is significant when many people are involved. So it’s unsurprising that software development teams have created tools to manage this over the years. The committer is done once she gets the notification — usually an email. Fix Broken Builds Immediately. A crucial part of the continuous build must be fixed immediately if the mainline build fails.

Continuous Integration is a widespread technique in software development. The whole point of working with CI is continuously developing on a known stable base.

[¹]: Continuous Integration: Improving Software Quality and Reducing Risk