continuous integration is dead
TRANSCRIPT
![Page 2: Continuous Integration is Dead](https://reader031.vdocuments.mx/reader031/viewer/2022030303/587c16e61a28abb5068b4767/html5/thumbnails/2.jpg)
master
#45
#14
CIserver
Broken
Clean
![Page 3: Continuous Integration is Dead](https://reader031.vdocuments.mx/reader031/viewer/2022030303/587c16e61a28abb5068b4767/html5/thumbnails/3.jpg)
“Crucially, if the build fails, the development team stops whatever they are doing and fixes the problem immediately”
Jez Humble, p.55
![Page 4: Continuous Integration is Dead](https://reader031.vdocuments.mx/reader031/viewer/2022030303/587c16e61a28abb5068b4767/html5/thumbnails/4.jpg)
Who Needs This?
CEO
architect
authordevelopers
productowner
![Page 5: Continuous Integration is Dead](https://reader031.vdocuments.mx/reader031/viewer/2022030303/587c16e61a28abb5068b4767/html5/thumbnails/5.jpg)
Option #1: Ignore it
![Page 6: Continuous Integration is Dead](https://reader031.vdocuments.mx/reader031/viewer/2022030303/587c16e61a28abb5068b4767/html5/thumbnails/6.jpg)
Option #2: Enforce it
1.blame2.fear
3.long branches4.throw-away
5.losses
![Page 7: Continuous Integration is Dead](https://reader031.vdocuments.mx/reader031/viewer/2022030303/587c16e61a28abb5068b4767/html5/thumbnails/7.jpg)
master
#45
#14
CIserver
Clean
pre-flight bot
Pre-Flight Builds
![Page 9: Continuous Integration is Dead](https://reader031.vdocuments.mx/reader031/viewer/2022030303/587c16e61a28abb5068b4767/html5/thumbnails/9.jpg)
1. 95% builds are green 2. No fear of breaking master 3. No blame, no stress 4. Quick and small branches
![Page 10: Continuous Integration is Dead](https://reader031.vdocuments.mx/reader031/viewer/2022030303/587c16e61a28abb5068b4767/html5/thumbnails/10.jpg)
What do you think?
BTW, it’s a good moment to follow me: @yegor256
and check my blog: www.yegor256.com