When Failure Is Not an Option: From Fully Manual to Slack-based Deployments at ITIVITI
summary
ITIVITI replaces a manual pipeline with a mixed build/buy stack (Gerrit, Jenkins, XebiaLabs plus a homegrown clone exact replica tool) and a JavaScript deploy bot via Slack that triggers CI checks, creates tickets, notifies clients and schedules runs. Outcomes: more than 2,000 deployments per month, mean deploy time drops from ~30 minutes to ~5, production success rises 98% to 100%, change throughput more than doubles while production headcount increases by only one.
AI-written summary · about
chapters (21)
- 0:00Intro
- 0:38Introductions
- 1:51Who is ITIVITI
- 4:10Client Services
- 4:44Why is failing not an option
- 5:39Before DevOps
- 8:45Challenges
- 10:14Solution Stack
- 12:52Zilla Labs
- 13:58Automation
- 15:53Outcomes
- 17:36Whats next
- 19:05What did I learn
- 21:39Pains and tears
- 22:48Development team
- 24:00Every deployment is successful
- 25:35What were the challenges
- 26:50Financial business case
- 27:51Client satisfaction
- 28:49Rules
- 30:14Conclusion
related talks
01h 01mA team's transition to Continuous Delivery
26mHuman Trust in Continuos Deployment
28mDOES14 - Bill Donaldson and Aimee Bechtle - The MITRE Corp
54mFrom Code to Customer
01h 12mPitfalls of Continuous Deployment
43mServing for the win - Deploys and hosting for the rest of us
46mThe Software Factory
35mDevToDeploy: Integrate Your PM & CICD Tool For Systematic & Faster SW Delivery