Building an end-to-end DevOps pipeline

on YouTube ↗05m

" summary

Cross-functional teams replace ticket silos with an application manifest that contains CI, infrastructure and deploy metadata; the pipeline runs from git commit through release orchestration 2 and uses manifest-driven deploys so developers trigger CI/CD without scripting. Results: build time 1.6 minutes, complete CI in 4 minutes, release to UAT in 6 minutes, recovery time 30 minutes, meantime to release 3.4 days, over 1,000 applications on the pipeline and a shift metric reported as 1.56.

AI-written summary · about

" chapters (4)

1. 0:00Introduction
2. 1:14Crossfunctional Agile Team
3. 2:29Empowering Developers
4. 4:15Results

" related talks

• 01h 01mA team's transition to Continuous DeliveryAshley Noble · NDC Sydney 2017
• 30mBringing DevOps Success to Every App, Tool & Role in Your OrgRobert Stroud, Kurt Straube · DevOps Enterprise Summit London 2018
• 33mContinuous Delivery Pipelines: How to Build Better Software FasterDave Farley · GOTO Copenhagen 2021
• 21mValue of DevOps Release Process in Data TeamsFALEK MIAH · SQLBits 2024
• 46mDevOps Pipeline GameJorge Luis Castro Toribio · DevDays Europe 2024
• 33mFrom 0 to DevOps in 80 daysRoman Spitzbart · DevOps Inspire 2018
• 27mThe Five Phases of DevOpsJoel Vasallo · devopsdays Chicago 2016
• 28mDOES14 - Bill Donaldson and Aimee Bechtle - The MITRE CorpBill Donaldson, Aimee Bechtle · DevOps Enterprise Summit 2014 (San Francisco 2014)