Empowering Continuous Delivery with Spinnaker: A State of th...
summary
Spinnaker outlines concrete outcomes: an implemented CD events spec for loose coupling, a completed monorepo that collapses 11 services into single PRs but awaits Gradle/npm credential fixes, and a new account management API that adds deploy accounts without restarts. A shipped artifact store moves large baked manifests to S3 references, shrinking many pipeline executions to ~38% of prior size and cutting average payloads roughly in half. Also delivered: Java17 modernization, a test harness, compression in Orca, and a code-first pipeline Builder.
AI-written summary · about
chapters (12)
- 0:00Spinnaker introduction
- 1:45CD event integration strategy
- 3:28Managing Spinnaker microservices
- 4:54Spinnaker testing and performance
- 6:40Spinnaker security and scalability
- 7:42Spinnaker account management API
- 9:08Spinnaker error reporting improvements
- 9:51Java pipeline Builder
- 11:15Spinnaker community support
- 12:19Spinnaker artifact store
- 16:54Spinnaker pipeline compression
- 17:59Q&A
related talks
43mAll Aboard: Transforming Software Delivery Using Spinnaker
34mSpinnaker Technical Oversight Committee Panel
05mOvercoming Organizational Challenges in Continuous Delivery with Spinnaker
48mContinuous Delivery with Spinnaker
36mOrganizational Challenges of Implementing Continuous Delivery w/ Spinnaker
31mHow Spinnaker is Shaping Delivery Excellence at SAP
16mSpinnaker State of the Union (Opening Keynote)
08mSpinnaker as Code SIG Update