Migrate Legacy Deployment Orchestration to Spinnaker
summary
Migrates deployment from TeamCity (CI+CD) to Spinnaker as CD, installing Armory Spinnaker, enabling pipeline as code in GitHub and role-based access control, and moving ~20+ services across 5+ environments. Pipelines are standardized, TeamCity retains only builds, Spinnaker triggers deploys, enforces manual judgments for production, integrates automated post-deploy tests, disables legacy deploy jobs, and ties pipelines to issue tracking. Result is fewer manual steps, enforced change control, and higher release reliability and efficiency.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:31Legacy CI/CD challenges
- 4:02Spinnaker architecture overview
- 5:53Installation and setup
- 7:43Preparation phase details
- 10:17Construction phase process
- 14:28Pipeline complexities
- 17:00Release enhancement phase
- 18:47Conclusion and results
- 20:13Q&A
related talks
22mPractices for Applications Migration to Spinnaker
43mAll Aboard: Transforming Software Delivery Using Spinnaker
50mSpinnaker get control over your deployements
48mScaling a Migration to CD at Airbnb
31mHow Spinnaker is Shaping Delivery Excellence at SAP
05mOvercoming Organizational Challenges in Continuous Delivery with Spinnaker
53mContinuous Deployment with Spinnaker — Automate All Your Deployments!
23mPolicy-driven Deployments in Spinnaker