Spinnaker at Salesforce: Enterprise-Level Multi-Substrate Continuous Delivery and Release Management
summary
Salesforce runs about four Spinnaker instances across three cloud substrates with roughly 30–50k pre‑prod executions per day and 5–12k in production, managing ~1,000 apps, 50–60k generated pipelines from 5,000 templates. Pipeline generation is GitOps from environment BOMs into deployment manifests and master pipelines; Terraform orchestrates infrastructure changes; Kayenta is planned for canaries. Failures use idempotent master pipelines that skip succeeded targets, support retries and automated rollbacks, and account scaling required custom init containers for clouddriver/rosco.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:04Spinnaker: Footprint
- 1:17Instances and execution
- 3:53Apps, templates and guidelines
- 4:44Pipeline types
- 6:24Salesforce Journey: Challenges
- 6:39Challenge 1: Pipeline templates
- 8:54Challenge 2: Release across multiple environments
- 10:00Challenge 3: Change management
- 11:50Challenge 4: Failure handling
- 13:40Challenge 5: Infrastructure builds and changes
- 14:32Challenge 6: Spinnaker account management
- 15:24Challenge 7: Alerts and notifications
- 15:58Challenge 8: Pipeline security
- 16:50Challenge 9: Handling promotions
- 17:40Challenge 10: Complex release orchestration mechanism
- 18:14Roadmap: Future Projects
- 18:48Q&A
related talks
36mSpinnaker - Land of a 1000 Builds
25mEnabling Diverse Application Use Cases using Spinnaker
28mSalesforce Status Report – What Are We Up To With Spinnaker?
33mPanel Discussion: Spinnaker Success - CD as a Service using Spinnaker
29mScaling Spinnaker for multi-region multi-cloud SaaS deployments
52mContinuous Deployment to the Cloud using Spinnaker
48mContinuous Delivery with Spinnaker
30mSpinception: Deploying Spinnaker with Spinnaker