Incubating Continuous Delivery
summary
Describes a hands‑on program that builds a company‑specific CD maturity matrix, links to CI/CD recipes, rolls out dynamic templates and shared pipeline libraries, and enforces feature‑flagging and a GitHub‑flow style branching model; picks a CI/CD engine based on dashboarding, infra support, pipeline‑as‑code, customization and extensibility. Notes a painful template/versioning tradeoff, a real scale of ~200 pipelines, and that high‑quality libraries plus rollback plans make the approach work in practice.
AI-written summary · about
chapters (7)
- 0:00Start
- 5:41Disclaimer
- 17:00Difference between Code Deployment and Release
- 22:54Community of Practice
- 28:17Ci Cd Recipes
- 31:56Dynamic Templates
- 45:00Extensibility
related talks
28mMinimum Viable Continuous Delivery
24mWhy, What, and How of Continuous Delivery
34mBeyond Continuous Delivery
11mCreate unfair competitive advantage w/CI/CD Pipelines
30mModern Continuous Delivery
38mContinuous Delivery, or the magic button for on‑demand releases
28mContinuous Integration and Continuous Delivery Pipelines for Beginners and Managers
23mCI/CD: Conscious Uncoupling
