Continuous Delivery and InnerSource - Why you Should be Doing Both
summary
BBC iPlayer & Sounds runs shared CI/CD pipelines and a deployment tracker that annotates releases and measures deployment frequency and lead time; a lightweight auth tool called proxy simplifies S3 access; GitHub checks, labels and a release generator produce automated release notes and enforce review and merge rules. Over 30 teams move from hundreds of bespoke deploys to many releases a day, inner source contributions add features (telemetry, time‑range metrics) that scale across consumers, and measured throughput and shorter lead times show faster, more confident delivery.
AI-written summary · about
chapters (8)
- 0:00Start
- 1:13InnerSource is the use of open source best practices for software development within the confines of an organization.
- 1:31Our Continuous Delivery Journey So Far
- 3:40Deployment Frequency Change Lead Time Mean Time to Recovery Failure Rate
- 4:03Supporting a large number of teams
- 4:27Make services as easy to use and integrate with as possible
- 9:00Why you should InnerSource your CD tooling
- 11:37Why you should CD your InnerSource
related talks
33mScale your CI/CD setup for Cloud Native Microservices via InnerSource
36mAvoid Chaos in Our CI/CD Pipelines with Inner Source
30mOur Continuous Delivery Journey
51mBetter software, faster: principles of Continuous Delivery and DevOps
01h 01mA team's transition to Continuous Delivery
41mAll Things Continuous
24mWhy, What, and How of Continuous Delivery
41mShift Left, Shift Right and Improve the Centre