Quickly Test Your Kernel with GitLab CI
summary
GitLab CI pipelines are configured to build kernels for arm32/arm64/x86_64, run IGT GPU tests on specific lab devices, and report per-driver expected failures, flakes and skips so fixes show history; the DRM pipeline (called MCI for DRM) runs container→build→per-driver stages on freedesktop runners but competes for shared devices and priority. A generic patch set (KCI GitLab) adds a root .gitlab-ci, container and static-check stages, and scenario overrides so subsystems can define custom jobs; documentation explains how to enable pipelines, add runners, and the current blocker is community adoption and merging.
AI-written summary · about
chapters (16)
- 0:00Kernel testing with GitLab CI
- 1:29Traditional workflow limits
- 8:05GitLab CI fills gaps
- 9:11DMCI implementation
- 13:35DMCI for kernel testing
- 17:54DMCI limits and KCI motivation
- 18:57KCI GitLab intro
- 21:50KCI GitLab out of box
- 23:37Extending KCI with tests
- 26:27KCI future and feedback
- 28:35Pre-merge testing call
- 31:37Q&A: Virtualization & VMs
- 34:34Q&A: Historical test data
- 36:17Q&A: Pipeline rules
- 37:22Q&A: Future priorities
- 38:52Closing remarks
related talks
18mSimple KernelCI Labs with Labgrid
35mManaging CI Across Multiple Farms for GPU Testing
39mKDEs CI and CD Infrastructure
27mPlugging into the Red Hat kernel CI ecosystem
38mQuality Beyond Kernelci.Org in Upstream Linux for TI SoCs
26mRISCV patchwork CI
15mDocker image testing in GitLab CI
26mOptimizing Your CI Pipelines