Cookies for Kernel Developers
summary
Red Hat’s CKI ("cookie") runs an automated CI that pulls series from mailing lists via patchwork, merges patches into test trees, builds kernels across multi-arch: x86_64, arm64, ppc64le, s390x, and boots them on real hardware managed by Beaker + OpenShift orchestration. Results post as tarballs and mails (successes to lists, failures to senders); tests include LTP, KVM/virt and others. It already catches regressions (multi-arch compile break stayed undetected for weeks) and even a deliberate panic before release.
AI-written summary · about
chapters (23)
- 0:00Introduction
- 0:30Who is Nikolai
- 1:07What is Cookie
- 1:36Emoji for Cookie
- 2:09Maintaining Stable Kernel
- 3:13Stable Kernel Release
- 3:40Linux Distribution Maintainer
- 4:39Bug Reports
- 4:58Additional Questions
- 5:26Patchwork
- 7:50The Bigger
- 8:59Target Tests
- 9:32Test Suites
- 11:12Upstream Kernels
- 12:41Feedback
- 13:30Hardware Testing
- 13:53Gregs Workflow
- 15:59What we are working on
- 18:24Send us an email
- 18:51Send us a message
- 19:45Why is Red Hat doing this
- 20:30Get involved
- 21:05Intels BOTS
related talks
34m7 Ways to Make Kernel Developers Like Cookies
27mPlugging into the Red Hat kernel CI ecosystem
36mKernelCI - How Can It Impact Your Future?
26mRISCV patchwork CI
38mQuality Beyond Kernelci.Org in Upstream Linux for TI SoCs
12mKernelCI kci-dev: Closing the developer feedback loop
30mRHEL Kernel Workflow using GitLab
29m(Ab)using GitHub Actions for building & testing kernels