KernelCI for Embedded: Enhancing Reliability through Scalable Test Automation
summary
KernelCI runs a scalable test pipeline for embedded Linux with a web dashboard (d.kernelci.org), a Maestro orchestrator of small services, and a results store moving from KCIDB to KCIDB NG. Labs send results (currently a few LAVA labs; non‑LAVA support now possible), artifacts sit in Azure blobs, and a kci.dev CLI lets developers submit jobs and fetch results. In‑tree kernelci.yaml and a pipeline API let unmerged patches be tested; the new system is deployed and stabilizing with improved extensibility.
AI-written summary · about
chapters (18)
- 0:00KernelCI introduction
- 1:51Beyond simple CI loops
- 5:10KernelCI components status
- 7:20Web dashboard insights
- 9:51KCIDB and labs
- 12:23Maestro orchestrator
- 15:12KernelCI user roles
- 16:16Maintainers notifications
- 18:50Developers test control
- 22:21QA environment customization
- 24:12Lab hardware integration
- 27:07KernelCI pipeline refinements
- 28:35YAML files for maintainers
- 30:48Pipeline API enhancements
- 31:51Try KernelCI now
- 33:38Community feedback
- 34:44KernelCI future vision
- 36:09Q&A
related talks
34mMerging your Kernel Testing Code into KernelCI
40mGetting Started With New KernelCI CLI Tools for Automating Linux Kernel Testing...
40mOne year into the new KernelCI
33mKernel CI – How Far Can It Go?
37mKernel CI – How Far Can It Go?
33mMerging an existing framework into KernelCI
38mQuality Beyond Kernelci.Org in Upstream Linux for TI SoCs
34mLinux Kernel Testing: Providing Better Results to the Upstream Community