Living on Master: Using Yocto Project, Jenkins and LAVA for a Rolling Release
summary
Build system that continuously compiles a full Yocto distribution and runs hardware tests, using Yocto Project, Jenkins, LAVA together; upstream metadata auto-sync runs daily and every commit triggers a build so images and kernels are built 100% each night, with a weekly promoted release. A 16-device boot farm flashes images over network boot, runs PyTest-based tests and returns JUnit results to Jenkins, and the setup generally works while producing large log volumes that need Elasticsearch-style analysis.
AI-written summary · about
chapters (20)
- 0:00Intro
- 2:01Fork it and forget it
- 3:45Future technical debt
- 5:07Linux kernel release model
- 6:32Everyone has a solution
- 7:10Motivations for this project
- 9:28System of review
- 12:05Repository layout
- 14:52Automation
- 16:18Booting
- 21:04PITest
- 22:31Industry Standards
- 25:53Moving forward
- 26:12Enterprise class reference
- 30:20Where will it be hosted
- 33:11How often does it happen
- 37:38System detective lecture
- 41:24How brittle is it
- 43:11Rolling releases
- 45:33CI builds
related talks
37mAutomated Testing and Continuous Integration/Delivery: Lessons Learned
29mTesting, a Journey from Testing Kernels to Testing Debian and Yocto
39mTesting Your Yocto Proj: from Ptest & Testimage to LAVA
52mCreating Continuous Delivery for Yocto Based IoT Distribution
32mBuilding and Testing an Automotive Platform - How Automotive Grade Linux is Built and Tested
50mUsing the Yocto Autobuilder for Build and Release Management
33mLKFT experiences and plans
45mUpdate on LAVA Testing for bare metal systems