Using packit and testing farm for CI/CD and automation in an upstream project

on YouTube ↗14m

" summary

Packit runs a build for every merge as daily builds per commit, performs PR builds in temporary COPR repos (kept ~7–14 days), and invokes Fedora Testing Farm via TMT to run VM tests for storage workloads; it also triggers reverse‑dependency testing (e.g., cockpit runs against udisks) and automates downstream work by creating Fedora pull requests, kicking off Koji builds and Bodhi updates. Small configs (around five to six YAML lines) enable all this and save roughly an hour per manual Fedora release workflow.

AI-written summary · about

" chapters (10)

1. 0:00Packit introduction
2. 1:03Upstream/downstream automation
3. 2:27Daily COPR builds
4. 3:53PR builds in COPR
5. 4:36Testing Farm VM testing
6. 6:22Reverse dependency workflow
7. 7:50Fedora downstream automation
8. 10:23Packit features
9. 11:28Packit for maintainers
10. 12:22Q&A

" related talks

• 30mPackit: RPM integration, all in oneLaura Barcziová, Matej Focko, Maja Massarini · DevConf.CZ 2023
• 48mIntegrating upstream projects downstreamTomáš Tomeček · DevConf.CZ 2020
• 26mTesting Github PRs on Fedora/Centos with PackitMiroslav Vadkerti · DevConf.CZ 2020
• 35mPackit: 2 years of upstream ⟷ downstreamTomáš Tomeček, František Lachman, Hunor Csomortáni · DevConf.CZ 2021
• 01h 05mFedora CI MeetupMichal Srb, Aleksandra Fedorova, Miroslav Vadkerti, Fabien Boucher · DevConf.CZ 2021
• 24mAuto - maintain your PackageStef Walter, Tomáš Tomeček · DevConf.CZ 2019
• 25mCI/CD for Fedora packaging with ZuulFabien Boucher, Matthieu Huin · DevConf.CZ 2020
• 50mDo our development tools need a refresh?Langdon White, Tomáš Tomeček · DevConf.CZ 2019