Flock to Fedora 2025

During the last couple of months, the Packit team has been working hard on providing a better CI experience for dist-git pull requests. Let’s take a look at how it works, and how you can tweak it to your needs. You’ll also learn how it fits the whole ecosystem and how the default setup is defined so you can suggest improvements.

No worries, we are not reimplementing a wheel. – We are building on the experience and solutions developed for upstream testing; most importantly, we use Testing Farm and tmt as a base for this so your test setup can be preserved. During the talk, you’ll also learn some news from the Testing Farm team about the test execution itself.

We have learned a lot from automating the package releases and one thing in particular – to be successful we need to listen to you and be responsive to the feedback. And we want to do the same for this new effort as well. So, come and bring your questions so we can make the whole system better together. We have plenty of ideas on how to improve it but maybe we are wrong about the importance - come, and tell us what is the most crucial to you. Help us not to forget about use cases like yours we might have forgotten about.

The aim of this session is to inform you about the changes in the Fedora dist-git pull request CI and to gather feedback and input for our future work.

Testing Farm is working on splitting the test environment setup for Fedora CI, CentOS Stream CI and Packit.

This will make the test environment setup visible to the end users and easily usable for local execution when reproducing CI failures. Moreover, the test environment setup will become easily contributable by the community, so the users will be able to influence the test environment setup by submitting a merge request.

Upstream project: https://gitlab.com/testing-farm/profiles