Our Continuous Delivery Journey
summary
Shows concrete outcomes: reduced release-end testing from ~25% of a quarter to ~5% (days not weeks) by moving installer tests earlier and automating them, which pays back within a year and makes a cloud rollout trivial while retaining a manual production gate. Describes tooling and architecture choices—Snap CI, GitHub, RabbitMQ, Nagios, containers, GoCD/CruiseControl—and a failed early push to nine microservices by a tiny team that is rolled back into fewer components to regain deploy frequency and reliability.
AI-written summary · about
chapters (29)
- 0:00Introduction
- 0:53About Suzie
- 1:35About Thoughtworks
- 1:55Top Companies 2016
- 3:29Continuous Delivery Book
- 4:00Continuous Delivery
- 6:45Continuous Delivery vs Continuous Deployment
- 7:49What is Mingle
- 9:01Our Continuous Delivery Journey
- 9:26Continuous Integration
- 10:47Feature Toggling
- 11:22Release Cycle
- 12:09Automate Installer Tests
- 12:58Process Changes
- 13:32Testing
- 13:58Hidden barriers
- 15:31Moving to the cloud
- 16:49Automation
- 18:01Snap
- 19:35Pre Services
- 21:09Microservices
- 22:15Cognitive Overload
- 24:08Key Job
- 25:12Takeaway
- 25:30Practice Continuous Integration
- 26:22Frequency Reduces Difficulty
- 27:03Moving Up
- 27:54Ask Bigger Questions
- 28:39Automate
related talks
28mClimbing the Mountain of CI/CD: A Tester’s Tale
01h 01mA team's transition to Continuous Delivery
32mClimbing the Mountain of CI/CD: A Tester’s Tale
24mWhy, What, and How of Continuous Delivery
32mContinuous Delivery Sounds Great But It Won’t Work Here
55mThe Rationale for Continuous Delivery
28mMinimum Viable Continuous Delivery
30mModern Continuous Delivery