Rawhide packages gating, things got real, for real
summary
Fedora gates Rawhide updates using Bodhi, Koji and Greenwave so single- and multi-build updates now block on CI results (CentOS CI → results DB) and are deployed to Bodhi staging and production; multi-builds use side tags that Koji signs then Bodhi marks testing-pending. There is an escape hatch to wave tests with permission, basic end-to-end camera tests run to catch pipeline breakage, and known problems are Koji query performance, noisy emails, and lack of reverse-dependency testing on the roadmap.
AI-written summary · about
chapters (21)
- 0:00Intro
- 0:45Agenda
- 1:28Why get rawhide
- 2:57Challenges
- 5:16Builds gated
- 5:49Single build
- 6:40Simplified flow
- 8:29Multibuilt
- 8:59Simplified
- 10:43Updated Modi
- 11:24Greenwave
- 13:22Tag changes
- 15:27No tags
- 16:12Side tags
- 17:04Update UI
- 18:08User feedback
- 22:17Roadmap
- 24:28CI Special Workshop
- 24:55Camera Testing Suit
- 28:18Stable Side Tags
- 29:18Questions
related talks
30mPackit: RPM integration, all in one
14mUsing packit and testing farm for CI/CD and automation in an upstream project
13mTake The Scare Out of Using Fedora Rawhide
29mTowards stronger checks on dependencies and compose inputs in Fedora
01h 05mFedora CI Meetup
15mFedora Zuul CI - an update
38mSIG Release - Deep Dive: Release Engineering Subproject
51mWrite tests for the Always Ready Operating System