Bridging the Gap Between Ops and Developers with CI/CD
summary
Argues that CI/CD plus automation cuts cycle time from months to days and enables thousands of releases per month (Scotiabank example), uses GitHub Actions, Spring Cloud Pipelines and Spring Boot Actuator for pipelines and observability, and teaches deployment patterns — rolling, blue/green, canary and A/B — with error budgets (example: two nines → 1% budget). Cites real outages and a Night Capital loss to show manual processes fail, claims automation lowers MTTR and saved teams up to 61% cloud cost by turning off idle services.
AI-written summary · about
chapters (15)
- 0:00Introduction and context
- 3:10Traditional software silos
- 7:22Automating testing
- 9:52Operations as software engineering
- 15:05Why automate everything
- 18:15CI/CD pipelines explained
- 21:43Deploy early and often
- 25:16Evolution of deployment strategies
- 31:59It depends: choosing strategies
- 36:37Shift left and reliability
- 40:26Cloud computing and costs
- 43:16Developer accountability
- 47:25Monitoring in distributed systems
- 48:46Site reliability engineering
- 49:08Q&A
related talks
59mBridging the Gap Between Ops and Developers with CI/CD
54mBridging the Gap CICD Mind the Gap
48mDemystifying CI/CD
39mRemove your Testing Bottleneck with CI/CD Pipelines
29mAutomating Continuous Compliance for Scalable SaaS Delivery
21mValue of DevOps Release Process in Data Teams
34mDeploy, Release, CI/CD, Oh My! DevOps for the Rest of Us
01h 02mTools and Techniques for Infrastructure as Code