Release management as a catalyst for CI/CD
summary
Organization starts a release-management program and moves from 50 to 300 releases year-over-year while cutting the rollback rate from 8% to 4%. Checklist-driven, scheduled deploys and a release manager create short-term predictability and let more engineers run deploys, exposing a Jenkins bottleneck and recurring manual bypasses. Parallel work on automated pipelines, testing and monitoring gradually replaces checklist steps, while stricter deadlines sometimes encourage risky manual work — trade-offs and concrete numbers show what practices accelerate CI/CD and which slow it.
AI-written summary · about
chapters (5)
- 0:00Start
- 0:09Release Management as a Catalyst for CI/CD
- 1:541. Checklists help track progress
- 3:401. Deadlines can lead to cutting corners and manual deploys
- 4:55Let's talk Release Management & CI/CD!
related talks
41mContinuous delivery in 10 easy mistakes
20mStreamlining Release Management for DevOps Success
40mSustainable Continuous Delivery: Patterns for rapid and reliable Releases
06mIgnite: Escaping the Black Hole of Release Management
59mBridging the Gap Between Ops and Developers with CI/CD
21mValue of DevOps Release Process in Data Teams
41mThe Pipeline-Driven Organization
17mA Brief History of Release Engineering