Why, What, and How of Continuous Delivery
summary
Argues that Continuous Delivery shifts business by making software the product and shows how to get there with concrete practices and tools: Jenkins automates the full pipeline, pipeline-as-code and CloudBees integration are used, and deployment techniques like blue‑green and canary deploys plus feature flags/testing in production contain risk. Cites surprising adoption metrics — installs rise ~37% to ~150,000 and build volume up ~40% to ~500,000 — and maps cultural gaps (team vs enterprise, dev vs ops) to specific automation steps.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 1:51Software disrupting industries
- 5:23Why continuous delivery matters
- 8:58Organizational culture shift
- 13:54Technology behind CD
- 20:14Jenkins as automation platform
- 23:04Conclusion and call to action
related talks
55mThe Rationale for Continuous Delivery
51mBetter software, faster: principles of Continuous Delivery and DevOps
31mThe Continuous Culture
19mModern Continuous Delivery
42mAutomation, Innovation and Continuous Delivery
27mAutomation, Innovation and Continuous Delivery
30mModern Continuous Delivery
45mBuilding Your Continuous Delivery Toolkit
