The Practices That Make Continuous Integration
summary
Claims 14 core practices (now 15, adding test reliability) enable true Continuous Integration; only two tools are strictly required: version control everything and automate the build. Concrete rules: everyone commits at least once a day, commit builds run in ~5–10 minutes, unit suite <30s, broken builds get fixed within 10 minutes. Techniques demonstrated: expand-contract (branch‑by‑abstraction), feature toggles and blue‑green deploys, layered fast unit/integration/acceptance tests. One cautionary example notes a toggle mishap that cost night Capital Services ~$460M.
AI-written summary · about
chapters (26)
- 0:00Introduction
- 1:00Being vulnerable
- 1:53Feature branching is evil
- 5:40Continuous integration certification test
- 6:33Continuous integration definition
- 7:42Continuous integration practices
- 8:47Version control
- 11:13First practice
- 12:01Communication tool
- 12:49Never break the build
- 16:06Team practices do not push to a broken build
- 17:07The most crucial practice
- 18:12Well revert when broken
- 19:54Critical engineering practices
- 20:07Make changes in small increments
- 21:45Decoupled code space
- 25:06virtuous circle
- 25:43testdriven development
- 27:21decoupled code
- 29:37large scale refactoring
- 35:37Release features incrementally
- 38:13Feature toggles
- 41:28Automated build
- 44:11Always working software
- 46:26High quality automated tests
- 57:11High reliable tests
related talks
46mContinuous integration - that's not what they meant
01h 05mTwelve Essential Practices to be Effective in Continuous Delivery
56mContinuous Integration: That’s Not What They Meant
32mBuilding Confidence Together: Continuous Integration & Testing
31mContinuous Integration 101 for Devs
34mContinuous Integration: A Bittersweet Love Story
45mContinuous Integration: That’s Not What They Meant
38mContinuous Integration May Have Negative Effects