Climbing the Mountain of CI/CD: A Tester’s Tale
summary
Organization moves from fortnightly to weekly production releases and hits the goal by year end; several concrete changes make it work. Built a small internal tool — Sentinel deploy UI — that installs any branch to test machines in ~2 minutes. Regression time drops from five to two days through outsource help, rotation of engineers and UX into testing, improved automation and flaky-test cleanup. Launch process adds ops on every team, a release coordinator, staging parity, AWS team machines; weekly deploys achieved and regression cut from five to two days.
AI-written summary · about
chapters (10)
- 0:00Start
- 5:01Product Managers
- 6:56The Obstacles We Had To Overcome
- 10:35Sentinel
- 12:02A Scheduled Release Meeting
- 14:57Other Tools
- 15:39Outsource Testing
- 23:16Mobile Apps
- 24:05Do We Use One Solution for Building As Well as Deploying
- 30:51How Did Going To Weekly Deploys Affect Our Sprint Cycle
related talks
28mClimbing the Mountain of CI/CD: A Tester’s Tale
30mOur Continuous Delivery Journey
01h 01mA team's transition to Continuous Delivery
53mTransforming testing methodologies: From manual to robust strategies
41mShift Left, Shift Right and Improve the Centre
47mFrom bi-annual to fortnightly releases in 4 months for 15 teams and one monolith
54mFrom Code to Customer
28mTestOps: A Journey to Story-Based Releases