Going Green: Getting and keeping your build pipeline greenWyn Van Devanter
schedule 1 year agoSold Out!
A build pipeline is such an important aspect of a software project. It saves a ton of manual, error-prone depoyment work, as well as results in higher quality software that can be released more frequently.
However, I have been on multiple projects where one of the steps in the continuous integration process was failing (red), often for multiple days or even perpetually. So much of the benefit a build pipeline provides is lost when this is allowed to happen. Bugs are not caught by automated tests; additional tests break without being fixed because no one notices; the culture of keeping a green pipeline diminishes and faith in everything from the pipeline itself to automated tests reduces. Developers learn bad habits.
Building the pipeline and getting all steps working (keeping it green!) is no small feat in the first place, and keeping it that way can also be a large undertaking. One way I have tried to combat this is to institute some specific process for the Scrum team, pertaining to monitoring and maintaining the build pipeline. There is also an aspect of convincing the team and management that it is worth spending the time, and dropping everything to maintain a fully functional pipeline.
Join me for a common sense, tactile approach to keep a build pipeline green that has worked on small and larger projects with multiple teams.