Bridging the Gap Between Ops and Developers with CI/CD
summary
Argues that CI/CD plus automation and SRE practices turn slow, siloed quarterly releases into repeatable pipelines with thousands of deploys a month as a realistic target, using CI, CD, blue/green and canary patterns, GitHub Actions and Spring tooling as examples. Recommends error budget of 1% to balance velocity and uptime and warns of catastrophic operational mistakes with a 460 million loss example, emphasizing automated rollbacks, observability and recoverability.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 3:15From silos to DevOps
- 9:54Why automation matters
- 20:28CI/CD pipelines explained
- 29:30Deployment strategies
- 41:20Cloud cost and accountability
- 48:40SRE and team alignment
- 54:33Q&A
related talks
55mBridging the Gap Between Ops and Developers with CI/CD
54mBridging the Gap CICD Mind the Gap
40mSustainable Continuous Delivery: Patterns for rapid and reliable Releases
05mRelease management as a catalyst for CI/CD
51mBetter software, faster: principles of Continuous Delivery and DevOps
41mContinuous delivery in 10 easy mistakes
21mValue of DevOps Release Process in Data Teams
48mDemystifying CI/CD