Integrating upstream projects downstream
summary
Packit automates building RPMs from upstream sources, running tests inside real VMs and sandboxed containers on OpenShift and continuously deploying to staging and Fedora Rawhide. It runs across 8 repositories and a production cluster with seven pods (three heavy worker pods), serves 100 projects and submits roughly ~10,000 builds/tests in six months. It requires or generates spec files, uses pre-commit hooks, records network interactions for CI replay, and faces outages from dependent Fedora messaging but deploys weekly.
AI-written summary · about
chapters (24)
- 0:00Intro
- 2:01Tomas
- 3:19GitHub
- 8:02Games
- 17:26Development
- 20:05Challenges
- 21:49Spec files
- 24:04Future
- 24:58Workshop
- 25:14QA
- 26:56Build RPMs
- 27:52Integration
- 29:27Request
- 30:28Priorities
- 31:32Document
- 33:30fedora with zu
- 34:14fork upstream
- 35:55can you integrate upstream projects
- 37:10Terms of service
- 40:07Requirement
- 41:47Help newcomers
- 42:53Working with spec files
- 44:05Perspective files
- 45:42Patch file
related talks
35mPackit: 2 years of upstream ⟷ downstream
30mPackit: RPM integration, all in one
14mUsing packit and testing farm for CI/CD and automation in an upstream project
24mAuto - maintain your Package
31mBreaking Barriers: Cross-Distro CI/CD with Packit and OBS
01h 00mRPMing Your Apps And Tools
01h 05mFedora CI Meetup
15mFedora Zuul CI - an update