Continuous delivery antipatterns
summary
Describes concrete anti-patterns and fixes: live-debugging production, two-day outage during peak causing “releases = risk”, missing version metadata and ad hoc deploys. Recommends semantic versions visible in production, keep a separate production repo and a binary repo (Artifactory/Nexus/S3) so builds compile once and store binaries, parallelize slow pipelines, test rollbacks with blue-green deploys, automate infrastructure with Chef/Puppet (use Foodcritic), use Vagrant/Docker for dev setup, exercise backups and practice rollback procedures, prefer stable master with short-lived branches.
AI-written summary · about
chapters (13)
- 0:00Introduction and speaker intro
- 2:41Non-technical problems in CD
- 5:09Lack of production visibility
- 10:29Fear of releasing causes stagnation
- 13:54Environment and pipeline issues
- 18:12Separate teams create barriers
- 25:16Manual infrastructure problems
- 29:10Dependency on internet
- 33:02Outdated runtimes and security
- 36:08Deployment failures and rollback
- 38:33State and partial failures
- 41:47Developer environment setup
- 44:15Q&A and closing
related talks
40mContinuous Delivery Anti-Patterns
17mDevOps Patterns & Antipatterns for Continuous Updates
41mContinuous delivery in 10 easy mistakes
55mPatterns & Anti Patterns for Scaling & Enabling DevOps Adoption
27mDevOps Patterns and Antipatterns for Continuous Software Updates
40mSustainable Continuous Delivery: Patterns for rapid and reliable Releases
05mDo this, not that: Antipatterns in Continuous Deployment
51mBetter software, faster: principles of Continuous Delivery and DevOps
