Creating Continuous Delivery for Yocto Based IoT Distribution
summary
Shows a working CI/CD pipeline for an Ostro Yocto distro using GitHub + Jenkins + Docker + combo-layer and an upstream-monitor that auto-creates pull requests, plus Jenkins Pipeline, Job DSL and Ansible provisioning for hundreds of jobs. Pull requests build on real hardware (builders in US, test devices in Finland), artifacts are promoted without rebuilding, and a build-history-extra class plus bemap and BeagleBone keyboard emulation catch regressions — the system finds multiple real bugs and scales to many layers.
AI-written summary · about
chapters (13)
- 0:00Start
- 3:44Stage Continuous Integration
- 4:28Continuous Delivery
- 5:31Source Code Management
- 8:27Configuration File
- 15:06Jenkins
- 17:45Jenkins 2 0 Feature the Pipeline
- 26:01Initial Provisioning
- 26:36Jenkins Job Dsl
- 29:37Tools
- 40:45Nightly Build
- 41:40Self Test
- 47:12Github Pull Request Builder
related talks
48mLiving on Master: Using Yocto Project, Jenkins and LAVA for a Rolling Release
28mContinuous Integration of C/C++ Apps for IoT Devices
37mAutomated Testing and Continuous Integration/Delivery: Lessons Learned
38mAutomating and Managing an IoT Fleet Using Git
52mBringing Continuous Delivery to Cloud-Scale with Jenkins, Docker and
12mCi in IoT/Embedded: creating a simple, salable and automated workflow
23mOrchestration and CI/CD
35mYocto Continuous Integration in a Kube