CI/CD - the game where all win!
summary
Company documents and an assessment model drive a concrete CI/CD plan: migrate source to Bitbucket/Git, wire builds and tests into Jenkins, require unit tests run on every commit and gate merges. The product is an embedded meeting-room device (Yocto Linux, C/C++, bash) that moves from six-month releases to sprint-by-sprint delivery, cuts testing/fix windows from 5/5/5 days to 11/1/1 in later phases, and ships as 13,500 units to enterprise customers.
AI-written summary · about
chapters (11)
- 0:00Introduction and agenda
- 0:54CI/CD fundamentals explained
- 3:03Principles of CI/CD
- 7:34Assessment model overview
- 11:36Using assessment model in practice
- 12:41Project case study introduction
- 15:56Development phase before CI/CD
- 20:56CI/CD implementation journey
- 25:55Results and benefits of CI/CD
- 28:04Before and after comparison
- 30:00Q&A and closing remarks
related talks
24mCI/CD Best Practices to Deliver Software Faster
33mCI/CD for Autonomous Drive and other complex systems - What we have learned about...
15mCI/CD: A History Lesson
28mDOES14 - Bill Donaldson and Aimee Bechtle - The MITRE Corp
44mSimplifying and Scaling Software Delivery
36mCI/CD BoF: Delivering Quality Quickly
37mAutomated Testing and Continuous Integration/Delivery: Lessons Learned
17mCI/CD - Build/Deploy Automation