How Spinnaker is Shaping Delivery Excellence at SAP
summary
SAP adopts Spinnaker as a central CD platform, building pipeline templates, a Git-driven landscape config, and a Jenkins wrapper to deploy and restore Spinnaker; the team integrates Jenkins, Gardener, Vault and Dynatrace and runs canary workflows across dev/stage/prod. Adoption tooling includes a self-service API to register clusters, CD starter-kits (pipelines-as-code) plus coaching, and the project reports 1000 deployments in six months, with automated restores and incremental canary rollouts.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 0:48Journey towards CI/CD
- 1:18Why Spinnaker?
- 3:21Several iterations
- 4:20Company numbers
- 4:46Spinnaker performance
- 4:57Struggles before Spinnaker
- 6:30How Spinnaker helps
- 8:34Example deployment of agent operator
- 10:20Spinnaker for application deployment
- 11:40Deployment pipeline
- 14:41How SRE supports these projects
- 14:58Architectural overview (Jenkins, Spinnaker, Kubernetes)
- 15:58Spinnaker landscape
- 18:09Implementing Spinnaker
- 20:23Self-service API
- 21:20CD Starter-kit
- 22:52Thank you/Contact
- 23:03Q&A
related talks
43mAll Aboard: Transforming Software Delivery Using Spinnaker
50mSpinnaker get control over your deployements
24mUsing Jenkins and Spinnaker to Supercharge Your Deployment Pipelines
18mOvercoming the challenges of using Spinnaker as a multi-tenant CD service
25mEnabling Diverse Application Use Cases using Spinnaker
33mPanel Discussion: Spinnaker Success - CD as a Service using Spinnaker
19m5 Reasons Spinnaker Aligns to FinServ Business Initiatives
48mContinuous Delivery with Spinnaker