From 100 Pipelines to 1
summary
Capital One consolidates hundreds of bespoke CI/CD flows into a single pipeline ecosystem that standardizes SDLC stages, enforces peer review, SAST and OSS scans, unit‑test coverage and architecture patterns, and provisions infra for APIs, UIs and databases. The central system integrates backend tools so cyber or test tool swaps require one change, not hundreds. Inner‑sourcing lets teams contribute shared features. Result: measurable compliance, better developer capacity and millions of deployments a year across 50,000+ associates and 10,000+ engineers.
AI-written summary · about
chapters (9)
- 0:00Intro
- 3:26Our DevOps journey - Early days
- 6:07Agile & YBYO model
- 8:14With great power came greater responsibilities
- 9:00Innovation gave birth to 100s of pipelines
- 13:55Pipeline tools reduced but challenges remained
- 17:12How to tackle these challenges
- 23:27Benefits
- 25:45Outro
related talks
25mDevOps at Capital One: Focusing on Pipeline and Measurement
29mBanking on Continuous Delivery
33mBanking on Innovation & DevOps
23mHow Shifting Left is Helping CapitalOne in its CICD Pro...
47mCreating a CI/CD Pipeline for Your Shared Libraries
49mOne pipeline to rule them all
07mCreating A Secure Software Supply Chain In A Large Engineering Organization
28mPush button deployments in minutes not months 🧭