All Just CI Theater
summary
The talk examines shortcomings of common Continuous Integration (CI) setups—teams that run Jenkins or similar but only perform CI superficially, creating a false sense of security called “CI theater.” It explains how to recognize CI-theater and recommends practical measures to move from shallow CI toward genuine Continuous Integration and thus enable Continuous Delivery.
AI-written summary · about
chapters (14)
- 0:00Start
- 4:4611 Practices
- 5:40Maintain a Single Source Repository
- 6:48Make Your Build Self-Testing
- 8:35Test in a Clone of the Production Environment
- 9:57Automate Deployment
- 19:34Fix Broken Builds Immediately
- 21:32CONTINUOUS DELIVERY
- 23:47Branch by Feature
- 26:32Continuous Isolation
- 27:00DON'T DO FEATURE BRANCHES!
- 27:55Trunk Based Development
- 29:52Branch by Release
- 31:59Keeping Your Application Releasable
related talks
34mContinuous Integration: A Bittersweet Love Story
38mCI is Essential but not Sufficient for an Effective Application Delivery Workflow
11mCreate unfair competitive advantage w/CI/CD Pipelines
46mContinuous integration - that's not what they meant
32mBuilding Confidence Together: Continuous Integration & Testing
45mBuilding Your Continuous Delivery Toolkit
01h 00mContinuous Intrusion: Why CI Tools Are An Attacker's Best Friends
23mKeynote: The Past, Present and Future of Continu...