Push button deployments in minutes not months 🧭
summary
Capital One migrates from months-long vendor rollouts to push-button production deployments measured in minutes by standardizing CI/CD, automating security and functional checks, and converging custom Groovy pipelines into a single reusable framework. They use Jenkins with shared libraries, build and test as a Docker image, run local and pipeline SAST/SCA scans, codify threat modeling, and require developers to write JUnit/Cucumber tests. Result: roughly 70% of pipelines auto-run to production and faster mean time to release.
AI-written summary · about
chapters (11)
- 0:00Intro
- 0:29CapitalOne
- 3:09State of Legacy Deployments
- 4:19Foundational Pillars
- 7:36Pipeline Evolution
- 9:42Custom Groovy Scripting
- 11:53Proliferation of pipeline frameworks
- 15:08Standardization across enterprise
- 17:00Shifting Left @ Capital One
- 19:34Security
- 23:02Automated Functional Testing
related talks
33mBanking on Innovation & DevOps
01h 01mA team's transition to Continuous Delivery
12mContinuous Deployment in a heavily regulated environment
01h 01mUnlocking Agile Efficiency: From Days to Minutes
26mFrom 100 Pipelines to 1
29mBanking on Continuous Delivery
34mEnabling a Continuous Deployment Mindset
23mHow Shifting Left is Helping CapitalOne in its CICD Pro...