Organizational Challenges of Implementing Continuous Delivery w/ Spinnaker
summary
At Lookout and now Autodesk a Spinnaker rollout follows POC (≈3–4 weeks), beta (≈2 months) and a six‑month push to GA, then ~1.5 years to onboard ~200 services. Replacing fragmented tooling yields 25 steps → 1–3 steps to deploy, reduces engineering deploy time from 60 min → <1 min, and shrinks onboarding from 3+ days → ~30 minutes. Compliance gates move left into GitHub approvals and platform design treats the CD platform as a product with community contributions (ECS provider) and commercial Armory support.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 0:46What is Continuous Delivery
- 1:13Implementing Continuous Delivery
- 4:45People
- 7:03Metrics
- 9:26Before After Metrics
- 11:46Decision Making
- 13:25Where Were We
- 13:49Our Problems
- 15:21Our Solution
- 18:16Why Spinnaker
- 23:22Compliance Security Controls
- 27:09DevOps Transformation
- 29:09Lookout
related talks
05mOvercoming Organizational Challenges in Continuous Delivery with Spinnaker
20mEmpowering Continuous Delivery with Spinnaker: A State of th...
33mEvolving a Continuous Delivery Workflow
48mContinuous Delivery with Spinnaker
31mHow Spinnaker is Shaping Delivery Excellence at SAP
33mPanel Discussion: Spinnaker Success - CD as a Service using Spinnaker
36mSpinnaker - Land of a 1000 Builds
34mSpinnaker Technical Oversight Committee Panel