Continuous Deployment in a heavily regulated environment
summary
A Node.js service at JPMorgan moves from manual quarterly releases to automated continuous deployment: first production deploy January 2017, now 200+ intraday releases and time-to-market drops from 3–5 weeks to 20 minutes. Pipeline-as-code uses Jenkins with the Pipeline plugin and Groovy, an internal shared Jenkins library, automated rollback and OSS vulnerability scans, and phased rollouts via Fisher flux. Tests focus on a small set of end-to-end checks; culture and approval changes are the other hard requirements.
AI-written summary · about
chapters (5)
- 0:00Start
- 1:44Banking software failures
- 4:31J.P. Morgan Markets
- 6:05Manual Change Management Process
- 8:39Continuous Deployment: mitigating risks
related talks
33mHow Our Continuous Delivery Platform Is Enabling the Public Cloud Migration Journey at JPMorgan Chase & Co.
55mContinuous Deployment Workflows for Modern JavaScript
49mThe road to continuous deployment: a case study
53mThe Road to Continuous Deployment: a Case Study
41mThe Pipeline-Driven Organization
01h 12mPitfalls of Continuous Deployment
01h 01mA team's transition to Continuous Delivery
27mAutomation, Innovation and Continuous Delivery