RHEL Kernel Workflow using GitLab
summary
RHEL moves from email patchwork to a merge-based GitLab workflow that ties every change to Bugzilla and requires a successful CKI gate before inclusion; merge requests spawn webhooks queued via RabbitMQ and processed on OpenShift, an email bridge converts MRs into patchset emails for legacy review, and artifacts and RPMs for multiple architectures are downloadable from CI. Command-line tools like lab CLI and getbackport automate MR creation and backport formatting, and kernel watch and acknack webhooks enforce per-subsystem reviews; rollout reduces maintainer triage but merge trains and data retention remain to solve.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 10:30Webhooks
- 13:05Continuous Integration
- 14:50ACKnack
- 15:30Review
- 16:40Fedora Kernel
- 17:05Closing Comments
- 17:55Questions
- 20:35Getting Developers to Understand
- 22:55Traceability
- 24:05GitHub
- 26:10Will it be adapted by kernel maintainers
related talks
35mKeeping the linux kernel secure across 10+ RHEL releases
24mEveryone can contribute to RHEL now!
27mPlugging into the Red Hat kernel CI ecosystem
39mQuickly Test Your Kernel with GitLab CI
35mCookies for Kernel Developers
37mIncident management for small service teams
34m7 Ways to Make Kernel Developers Like Cookies
10mLightning Talk: Leveraging GitOps - How Red Hat Delivers