Human Trust in Continuos Deployment
summary
Claim: human trust matters more than tooling for CI/CD. Teams build a continuous-deployment pipeline that ships 20–30 deployments per week, add a Jenkins promotion button as a manual gateway, and run weekly SRE meetings with blameless post-mortems to restore cross-team trust. A HipChat bot Trogdor the Continuous Deployment Sheriff nags when staging sits too long. Migration to AWS Application Load Balancer and a hard Oct 1 cutover for Craftsy 2.0 produce a one‑hour hotfix pushed three hours after launch, proving the approach works.
AI-written summary · about
chapters (13)
- 0:00Intro
- 0:34Disclaimer
- 0:54Who is Crafty
- 1:53Theme
- 2:23Trust
- 3:36Systems Trust
- 4:23Story Time
- 5:10Manual Deployment
- 8:33What Went Wrong
- 9:26What Worked
- 11:46Continuous Deployment Pipeline
- 14:43Trust in System
- 22:30Questions
related talks
28mClimbing the Mountain of CI/CD: A Tester’s Tale
34mEnabling a Continuous Deployment Mindset
41mAll Things Continuous
01h 01mA team's transition to Continuous Delivery
01h 12mPitfalls of Continuous Deployment
53mThe Road to Continuous Deployment: a Case Study
43mTo make mistakes is human. To auto-deploy it is DevOps.
47mContinuous Delivery Warstories