DevOps @ Fidelity - Investing in Inner Source and Engineering Excellence
summary
Fidelity documents a push to standardize pipelines, automate onboarding and embed security as continuous compliance, forbids any persisted production access so all changes flow through pipelines, and streams pipeline execution into an evidence store for realtime audit. An inner‑source model produces concrete results: five projects overall and a pipeline libraries/catalog that delivers 174 features with 3,500 commits from ~50 active contributors across 12 business units, used to reduce incidents while increasing change velocity.
AI-written summary · about
chapters (10)
- 0:00Topo Pal intro at Fidelity
- 2:09Topo Pal's role at Fidelity
- 5:02Fidelity's tech leadership
- 7:35DevOps and Cloud journey
- 8:59DevOps adoption challenges
- 11:46Tool standardization
- 13:53Compliance and security
- 16:47Metrics and measurement
- 18:58Inner Source at Fidelity
- 20:00Q&A
related talks
41mPanel Discussion: The Growth of InnerSource in Financial Services
40mNavigating FINTECH’s Regulatory Waters With InnerSource
15mFINOS and InnerSource
16mContinuous Delivery and InnerSource - Why you Should be Doing Both
28mDevOps, 12-Factor, and Platform Engineering
15mEngineering Culture and Developer Productivity
15mEmpathetic Engineering and InnerSource
26mIntel’s Journey to Large Scale DevOps Transformation