What do we know about continuous delivery – and what would we like to know
summary
A joint academia–industry study reviews literature and 15 company interviews and reports measurable claims: high performers report 50x more frequent deployments, far faster recoveries and fewer failures; Mozilla shrinks release cadence from 18 months to six weeks with no clear quality loss; cases show pipelines triggered per commit, virtualized test environments, and dedicated integration teams; common blockers are legacy architecture, resistance to change, and missing organizational practices like trunk‑based development and 30–40 deploys per day operational readiness.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 0:30Lars Bendix
- 2:36Network of Excellence
- 3:27Perception of continuous delivery
- 4:06Does continuous delivery work
- 5:39Continuous delivery discussion
- 7:05Research projects
- 8:05State of DevOps Survey
- 9:59IBM Whitepaper
- 11:48Obstacles to continuous deployment
- 13:57Open considerations
- 15:26Mozilla 6 week release cycle
- 16:53Continuous integration and Github
- 19:23Rapid release time
- 21:01Five steps to heaven
- 26:25Application Continuous Delivery
- 27:47Release Continuous Delivery
- 29:46Make
- 31:21Software Configuration Management
- 33:07Feedback
related talks
33mContinuous Delivery - What does good really look like?
40mSustainable Continuous Delivery: Patterns for rapid and reliable Releases
55mThe Rationale for Continuous Delivery
59mThe continuous culture
34mDevOps: Next
51mBetter software, faster: principles of Continuous Delivery and DevOps
28mMinimum Viable Continuous Delivery
31mThe Continuous Culture