Continuous Delivery in a Primeval Environment
summary
A travel business with 20 million customers, £8bn revenue and 22,000 staff moves legacy back ends toward continuous delivery by proving speed and trust: a new VM stands up in 5 seconds, a pipeline job in 15 minutes, and a cookbook takes ~two to three weeks to adapt. Tooling centres on Chef and Jenkins with Groovy DSL, public cloud and open source, while the delivery pattern is to extract small functions, push them weekly, and win the business off six‑month release cycles.
AI-written summary · about
chapters (15)
- 0:00Intro
- 2:12The Digital Age
- 4:45Release Every 5 Minutes
- 7:38Questions Answers
- 8:21Tools
- 14:07Automation
- 16:37Getting Started
- 18:07Cloud
- 19:27Suppliers
- 20:37Legacy Systems
- 22:52Digital Platforms
- 24:07PCI Compliance
- 25:52Security
- 27:42Skills
- 29:37Training
related talks
33mContinuous Delivery - What does good really look like?
32mContinuous Delivery Sounds Great But It Won’t Work Here
55mThe Rationale for Continuous Delivery
59mThe continuous culture
30mOur Continuous Delivery Journey
38mContinuous Delivery, or the magic button for on‑demand releases
31mThe Continuous Culture
55mContinuously Delivering Continuous Delivery