How We Decided the Time Was Now - Choosing Spinnaker
summary
Decision: replace Jenkins with Spinnaker to get reliable Kubernetes-aware deployments, keeping CircleCI for builds and artifact push while eliminating brittle Jenkins pipelines. Spinnaker’s built-in health checks and a manual judgment stage let the team mimic existing flows during rollout, starting with a POC and low-touch services and migrating 160 microservices. Tests are wired into pipelines so failures block progression, and the migration succeeds with engineers adapting well while work continues toward full continuous deployment.
AI-written summary · about
chapters (10)
- 0:00Introduction and team intro
- 1:03Legacy deployment system overview
- 2:49Jenkins pain points and limitations
- 4:15Why we chose Spinnaker
- 6:20Spinnaker’s Kubernetes advantage
- 7:44Implementation strategy and concerns
- 9:07Engineer adoption and feedback
- 10:29Next steps toward continuous deployment
- 11:51Current progress and future plans
- 12:12Lessons learned and advice
related talks
50mSpinnaker get control over your deployements
43mAll Aboard: Transforming Software Delivery Using Spinnaker
24mUsing Jenkins and Spinnaker to Supercharge Your Deployment Pipelines
31mHow Spinnaker is Shaping Delivery Excellence at SAP
48mContinuous Delivery with Spinnaker
30mSpinnaker as a Platform: Driving Cloud Adoption in Healthcare
33mPanel Discussion: Spinnaker Success - CD as a Service using Spinnaker
16mKeynote: Extending Jenkins with Spinnaker for a Multi-Target World