CI/CD for Autonomous Drive and other complex systems - What we have learned about...

on YouTube ↗33m

" summary

Complex vehicle CI/CD moves from slow emailed releases and SharePoint drops to an event-driven pipeline that uses a homegrown triggering system, RabbitMQ + Jenkins for transport and jobs, and object events for releases, activities and verification. The team faces 4.2 billion variants and shifts from 2–3 releases per year toward continuous integration, attaching confidence labels (green/red) to releases so pipelines auto-trigger, observability lets developers follow their change, and automation without centralization materially reduces manual handoffs.

AI-written summary · about

" chapters (6)

1. 0:00Start
2. 12:01Before events
3. 13:31Infrastructure
4. 17:17The activity event
5. 22:15Confidence labels
6. 28:20What will be better with CDEvents

" related talks

• 22mA Crawl, Walk, Run Story of CI/CDMathieu Leclerc · {unscripted} 2021
• 30mCI/CD - the game where all win!Admir Šatara, Ammar Karabeg · Bosnia Agile Day 2018
• 23mCI/CD: Conscious UncouplingBob Chen · {Unscripted} 2020
• 05mRelease management as a catalyst for CI/CDMorgan Meredith · DevOpsDays Chicago 2018
• 43mEffective CI/CD for Large SystemsJosh Reed · Berlin Buzzwords 2022
• 15mCI/CD: A History LessonKat Cosgrove · Jfokus 2022
• 30mOur Continuous Delivery JourneySuzie Prince · DevOpsDays Kansas City 2016
• 22mCI/CD is now AI/CDJonathan Vermeulen · ContainerDays Hamburg 2026