Continuous Delivery with Spinnaker
summary
Spinnaker plus Jenkins handles continuous delivery: Jenkins builds RPMs and Docker images, artifacts land in Artifactory or Google Container Registry, Spinnaker triggers pipelines from Jenkins or registry, bakes an AMI or deploys containers, creates load balancers and ASGs, runs automated QA, waits for manual judgment and audit approval (prod approval requires a second person), and supports 5,000 deployments/month at Gogo. Demo deploys a fixed-typo container to GKE (v1.9), runs an integration job against the canary, passes, and promotes to prod.
AI-written summary · about
chapters (14)
- 0:00Start
- 0:19Continuous Delivery with Spinnaker
- 1:05Continuous Delivery
- 1:34Core Tenants
- 2:50Immutable Infrastructure
- 3:52Benefits of Doing Continuous Delivery
- 10:39Spinnaker
- 15:30Cli Configuration Tool
- 19:37Demo
- 20:05Spinnaker Echo
- 27:13Configure the Deployment Cluster
- 30:48Rolling Pipeline
- 35:30Integration Test
- 46:26Foremast
related talks
50mSpinnaker get control over your deployements
24mUsing Jenkins and Spinnaker to Supercharge Your Deployment Pipelines
43mAll Aboard: Transforming Software Delivery Using Spinnaker
53mContinuous Deployment with Spinnaker — Automate All Your Deployments!
36mSpinnaker - Land of a 1000 Builds
52mContinuous Deployment to the Cloud using Spinnaker
31mContinuous Software Delivery Using Spinnaker and Jenkins in Cloud
31mHow Spinnaker is Shaping Delivery Excellence at SAP