Plugging into the Red Hat kernel CI ecosystem
summary
Red Hat integrates upstream kernel CI with real tools and measurable results: a CI engine called CKI ties tests into the beaker lab manager (Beaker), an ARK layer turns developer trees into distro builds, and DCI connects partner hardware labs behind firewalls. Tests run in a 2–4 hour window (about 90 tests across four arches) and uncover roughly 4–6 regressions per week. A central KernelCI Project database aggregates results so maintainers can correlate failures across vendors and labs.
AI-written summary · about
chapters (6)
- 0:00Start
- 0:01Plugging into the Red Hat kernel Cl ecosystem
- 13:36Automated testing service Built on gitlab pipelines Uses git trees and patches
- 15:29Defines configs and spec file Natural development environment How RHEL developers have worked for last 10+ years
- 17:29Utilizes Beaker Runs remote jobs Reports results to RH
- 21:04Ensuring the quality, stability and long-term maintenance of the Linux kernel Maintain an open source ecosystem around test and automation practices and principles for the Linux kemel.
related talks
35mCookies for Kernel Developers
33mKernel CI – How Far Can It Go?
40mOne year into the new KernelCI
36mKernelCI - How Can It Impact Your Future?
23mUnifying Kernel Test Reporting with KernelCI
33mMerging an existing framework into KernelCI
38mQuality Beyond Kernelci.Org in Upstream Linux for TI SoCs
31mFrom Jenkins-under-your-desk to resilient service