CI/CD - Build/Deploy Automation
summary
Claims that a true CI/CD practice is about cadence and policy not tooling and gives concrete targets: CI under five minutes, whole pipeline under fifteen and elite teams under an hour per DORA. Advocates replacing long-lived feature branches with trunk-based development, using pair programming for continuous review or a middle ground called fluid pull requests. Notes no specific pipeline tools are required and emphasizes measurable frequency (daily merges, daily deploys) and shorter feedback loops as the real deliverable.
AI-written summary · about
chapters (9)
- 0:00CI/CD introduction
- 1:16Continuous Integration
- 3:25Continuous Delivery vs Deployment
- 6:33Feature branch workflow
- 9:24Alternatives to feature branches
- 12:54CI/CD as practice
- 14:39CI/CD reading list
- 15:23CI/CD principles summary
- 16:48CI/CD misconceptions
related talks
24mCI/CD Best Practices to Deliver Software Faster
51mBetter software, faster: principles of Continuous Delivery and DevOps
11mCreate unfair competitive advantage w/CI/CD Pipelines
33mContinuous Delivery Pipelines: How to Build Better Software Faster
01h 01mA team's transition to Continuous Delivery
48mDemystifying CI/CD
40mContinuous Delivery Anti-Patterns
28mMinimum Viable Continuous Delivery