Continuous Delivery Anti-Patterns
summary
Argues that long-lived branches and big roadmaps block daily deployment, so teams remove branches, use feature toggles and progressive rollouts (example: 5% experiment), separate deployment from release, and run CI so production deploys are routine. Enforces TDD, pairing, testers who write code, strict test data management and service virtualization, plus staged pipelines that run virtualized suites then a reduced through-system smoke with fuzzy checks. Pushes environments as code (infrastructure as code) and a policy of fixing defects immediately.
AI-written summary · about
chapters (15)
- 0:00Start
- 6:37Continuous Integration
- 7:03Merge Hell
- 7:35Integration Week
- 8:07Branching
- 8:51Feature Toggle
- 9:09Progressive Rollout
- 11:55Test-Driven Development Is Essential or Continuous Delivery
- 20:47What Is Test Data Management
- 21:30What Happens When We Lose Faith in a Test
- 23:12Test Data Management
- 23:35Service Virtualization
- 24:29What Do We Do in a Continuous Delivery Mode
- 26:20Infrastructure as Code
- 39:05Keeping the Code Clean
related talks
46mContinuous delivery antipatterns
41mContinuous delivery in 10 easy mistakes
33mSoftware development practices for companies that want to make an impact
51mBetter software, faster: principles of Continuous Delivery and DevOps
46mContinuous Deployment Workflows
55mPatterns & Anti Patterns for Scaling & Enabling DevOps Adoption
40mSustainable Continuous Delivery: Patterns for rapid and reliable Releases
23mContinuous Deployment - The Last Frontier for Continuous Delivery
