Climbing the Mountain of CI/CD: A Tester’s Tale
summary
Moves deployment from biweekly to weekly by December 1 and sustains it for months, with 15 of 20 services on true continuous deployment and weekly releases at 11:00 a.m.; cuts a regression that used 7 testers for 3 days by adding developer time, Rainforest QA, automation and Git hooks; rebuilds testing on AWS production‑like environments; ships a small internal tool Sentinel to deploy branches, standardizes release roles, rotas and a dedicated Slack channel, and uses Jenkins.
AI-written summary · about
chapters (7)
- 0:00Introduction to CI/CD journey
- 6:32Setting weekly deploy goals
- 10:29Overcoming deployment obstacles
- 14:31Building testing infrastructure
- 21:36Solving regression testing problem
- 25:26Achieving weekly deployments
- 27:11Next steps for continuous deployment
related talks
32mClimbing the Mountain of CI/CD: A Tester’s Tale
30mOur Continuous Delivery Journey
01h 01mA team's transition to Continuous Delivery
42mTesting in a Continuous Delivery World
26mHuman Trust in Continuos Deployment
49mThe Whole Team Approach to Testing in Continuous Delivery
47mContinuous Delivery Warstories
41mShift Left, Shift Right and Improve the Centre