Volvo and Zuul CI
summary
Volvo makes Zuul the default CI and shifts from a garage setup to production: it scales from 200→600 projects, runs about 4500 jobs/day, averages ~150 active nodes and uses Gerrit, AWS/Azure and Kubernetes with Zuul v5, six schedulers and ten executors. Dependency-driven automatic rebuilds, semi-dynamic nodes and an enterprise-wide semaphore for proprietary licenses cut full-stack rebuild time from a week to 3.5 hours, and hardware-in-the-loop rigs validate real vehicle behavior.
AI-written summary · about
chapters (11)
- 0:00Introduction to Zuul at Volvo
- 1:18Scaling and infrastructure
- 3:28Build stats and recognition
- 4:43Customizations and tooling
- 7:06Dependency management
- 11:08Performance improvements
- 12:32Hardware in the loop testing
- 15:33Virtual ECU simulation
- 18:27Challenges and support
- 22:57Future roadmap
- 24:13Q&A and conclusion
related talks
15mZuul at Volvo Cars
43mThere is no Dana only Zuul
19mZuul CI for Kubernetes on the Workday Private Cloud
29mThe only easy day was yesterday (Zuul+Karpenter)
25mGetting Started with Zuul
48mTrunk Gating with Gerrit, Jenkins & Zuul
29mSimultaneous Dependencies with Zuul
24mUser Report of a Zuul Installation in Production