Happy Pipelines... No Need for Lifelines. J.P. Morgan: Our Sleek Approach to Adopt...
summary
J.P. Morgan migrates 4,000+ applications for 50,000+ engineers onto Spinnaker, hitting 85% ECS / 91% EKS deployment share by Q1 using a combination of blueprint modules, a migration team that scans repos and raises PRs, and OpenRewrite recipes that automatically refactor pipeline-as-code. A self-service pipeline template Marketplace plus an internal developer portal powers contributions. Outcomes: bulk migrations succeed at scale, evidence-store metrics track adoption, and recurring pain points remain—mutable pipeline state in a DB, single-branch pipeline-as-code contention, and plugin complexity.
AI-written summary · about
chapters (12)
- 0:00Spiner and modern pipelines
- 1:28Context at J.P. Morgan
- 3:15Adoption blueprints
- 4:41Customer-driven migration
- 6:06Pipeline template marketplace
- 7:31Migration lessons
- 8:56Spiner friction points
- 10:42Improving deployment tools
- 11:24Closing remarks
- 11:56Q&A session part one
- 12:38Q&A session part two
- 14:04Q&A session part three
related talks
33mPanel Discussion: Spinnaker Success - CD as a Service using Spinnaker
25mMass migrations to the cloud
18mHow to Build Your Digital Highway for Continuous Software Delivery
36mMigrating from kOps to EKS with Minimal Developer Involvement
40mScaling Startup for Success: Building modern Architectures and Developer Acceleration
20mRelease Engineering For A Polyglot Team
38mBuilding a Cloud Native Culture in an Enterprise - Deep Kapadia & Tony Li
27mThe next level pipelines delivering Net Zero