Continuous Delivery Best Practices
summary
Community-maintained best practices site lives on GitHub with a Learn section, contribution guidelines, issue tracker and examples to clone and PR; it documents definitions, CI/CD tool stacks and proposes GitLab CI workflows using git tags and PRs for build/test/deploy. Key claims: continuous delivery means software is deployable at any time while continuous deployment actually pushes live; testing strategy emphasizes ongoing rebuilds to avoid code rot and operating a tiny always-on canary at 1-2% for rapid failure detection.
AI-written summary · about
chapters (8)
- 0:00Introduction and overview
- 2:10Site walkthrough
- 6:43Version control and CI/CD
- 11:19Automated testing at scale
- 18:37Testing infrastructure costs
- 20:02Business alignment challenges
- 22:07Advice for small teams
- 23:09Closing and resources
related talks
01h 01mContinuous Delivery with GitLab CI and Kubernetes
01h 05mTwelve Essential Practices to be Effective in Continuous Delivery
24mWhy, What, and How of Continuous Delivery
30mModern Continuous Delivery
51mBetter software, faster: principles of Continuous Delivery and DevOps
55mThe Rationale for Continuous Delivery
49mIncubating Continuous Delivery
33mContinuous Delivery - What does good really look like?
