Continuous Integration May Have Negative Effects
summary
Claims that aggressive CI enforcement backfires and maps concrete failure modes across eight maturity levels including repo hygiene, automated builds, pull requests, code reviews, tests, static analysis and preflight. Names tools and fixes: git & GitHub, Maven/Gradle/Rake, artifactory or S3 for binaries, training or hiring build experts, policies for repos and reviews, breaking big repos into smaller modules, and pre-flight builds to block bad merges before they break the mainline. Practical, tool-level remedies and tradeoffs are enumerated.
AI-written summary · about
chapters (8)
- 0:00Intro
- 4:33Source Code Management
- 10:22Automated Build
- 15:57Pull Requests
- 22:57Code Reviews
- 26:52Unit Tests
- 32:20Static Analysis
- 33:57Preflight Build
related talks
34mContinuous Integration: A Bittersweet Love Story
01h 01mContinuous Integration: I Invite You to Break My Build
32mBuilding Confidence Together: Continuous Integration & Testing
01h 15mThe Practices That Make Continuous Integration
31mContinuous Integration 101 for Devs
32mContinuous Integration and Deployment: Five Lessons Learned
46mContinuous integration - that's not what they meant
45mContinuous Integration: That’s Not What They Meant