Testing 100's of OS Images with Jenkins: A Journey from Pull Request to Production Release
summary
Jenkins builds 90 balenaOS image types per pull request (about an hour) and hands artifacts to Leviathan, which schedules flashing and runs tests on Autokit hardware rigs. The pipeline runs 62 tests with 200+ assertions per image, taking ~90–120 minutes on embedded boards, and scales to 30–40 production releases per day. A real bug fix cycles from PR to customer-facing release in under 12 hours, demonstrating fully automated, hardware-in-the-loop delivery.
AI-written summary · about
chapters (11)
- 0:00Start
- 6:33The Pull Request
- 6:48Build them all!
- 8:12Freshly baked balenaOS
- 8:22Meet Leviathan
- 8:46Turning on the autopilot.
- 9:37Hardware in loop testing (HILT)
- 11:45Jenkins reports back results
- 12:03PR is merged
- 12:26Merge === Deploy
- 18:05And, that's about it!
related talks
48mLiving on Master: Using Yocto Project, Jenkins and LAVA for a Rolling Release
37mAutomated Testing and Continuous Integration/Delivery: Lessons Learned
35mMassively Continuous Integration: From 3 days to 30 minutes
35mTaming a beast
32mBuilding Continuous Integration and Feedback
29mOur Journey to Fully Automated Weekly Releases
45mHighway to Continuous Integration
20mRelease Engineering For A Polyglot Team