Better software, faster: principles of Continuous Delivery and DevOps
summary
Defines CI as frequent merges verified by automated builds and says builds must be fixed within ~10 minutes and pipelines should return feedback in under ~20 minutes. Recommends continuous deployment for small, frequent releases and feature toggles to separate deploy from release. Uses artifact stores (jar/war/container), DB migration tools like Liquibase/Flyway or backward‑compatible schema changes, and patterns like blue/green and canary releases. Shares concrete failures (cron truncated postcode table) and a metric that showed a “used a lot” feature only had 12 uses in three weeks.
AI-written summary · about
chapters (18)
- 0:00Welcome
- 3:40Continuous Delivery and DevOps
- 7:36Goal of Continuous Delivery explained
- 10:10Principles of Continuous Delivery
- 13:23CD culture and teams
- 15:52Design and architecture
- 18:16Pipelines and deployments
- 20:04Testing and automation
- 24:40Automation importance
- 25:23Non-functional testing
- 26:28Business value verification
- 30:45Reporting and insights
- 33:34Comparing Continuous Delivery and DevOps
- 36:49Common misconceptions and challenges
- 40:23CD and DevOps benefits
- 41:24Getting started with CD
- 42:09Quiz: Patterns vs anti-patterns
- 49:32Summary
related talks
40mSustainable Continuous Delivery: Patterns for rapid and reliable Releases
24mWhy, What, and How of Continuous Delivery
55mThe Rationale for Continuous Delivery
24mCI/CD Best Practices to Deliver Software Faster
40mContinuous Delivery Anti-Patterns
01h 05mTwelve Essential Practices to be Effective in Continuous Delivery
33mContinuous Delivery - What does good really look like?
31mThe Continuous Culture