Continues Integration Practices for Zephyr Upstream
summary
A CI pipeline for Zephyr upstream that glues Docker images, Jenkins Docker pipelines and a task queue to flash and run tests on real boards rather than simulators, using FTP URLs for artifacts and Blue Ocean YAML pipelines that spawn parallel builds. A stateless scheduler assigns board jobs, results land as URLs in a storage server, and board flashing uses an open pyMCU toolset (pyMCU-TK) plus J-Link support. System claims five-minute scaling to add Docker nodes and repeatable upstream validation without manual intervention.
AI-written summary · about
chapters (14)
- 0:00Intro
- 0:37Abstract
- 1:29Continues integration test in Zephyr
- 3:56User cases for upstream
- 6:56Requirements on a Cl system for upstream
- 9:49Dockers that are used
- 10:55Deployment
- 11:59Connect dockers
- 13:46Glue scripts
- 15:59Flash system
- 17:12Working process
- 18:45Examples
- 20:35Benefits
- 23:12Future work
related talks
33mContinues Integration Practices for Zephyr Upstream
32mLeveraging Cloud Technologies for Development and Operation of Zephyr
37mAutomated Testing and Continuous Integration/Delivery: Lessons Learned
52mCreating Continuous Delivery for Yocto Based IoT Distribution
29mZephyr Development Environment for Students
41mHands on Molding VS code into a care free development environment to develop with Zephyr RTOS
42mTaking Your Hardware to Production with Zephyr RTOS
06mBuilding Continuous Delivery Pipelines