Originally published at: Packit as Fedora dist-git CI: Phase 2 and 3 completed – Fedora Community Blog
Hello Fedora Community,
We are excited to share an update on the Packit as Fedora dist-git CI change proposal. This initiative aims to transition Fedora dist-git CI to a Packit-based solution, deprecating Fedora CI and Fedora Zuul Tenant. The change affects the triggering and reporting mechanism for tests but does not alter the tests themselves or the test execution service (Testing Farm). The transition is gradual, allowing maintainers to try the integration out, provide feedback and catch issues early. You can read more about the benefits and why we are doing this in the proposal itself.
What we have and how to use it
As part of the second and third phases, we have implemented Packit-driven installability checks and custom tests for Fedora dist-git PRs.
These features are currently opt-in, and maintainers can enable them by adding their projects to our configuration here by creating a pull request.
Once projects are listed in our packit-service configuration, Packit will automatically run a Koji scratch build and an installability check for every push to a dist-git PR.
Currently, the installability check executed by Packit is identical to the one performed by Fedora CI. In the future, based on user requests and already collected feedback we may plan to enhance it.
Additionally, if a project has both a .fmf/version file and a tmt plan defined in the plans directory, Packit will also execute custom tests in Testing Farm and report the results.
You can see an example of how this feedback appears in this python-specfile example PR or in the screenshots below:
Retriggering of all the jobs via pull request comments is also possible now, for details, see the documentation.
Do you want to know more? Look at our Packit as Fedora dist-git CI documentation.
Providing feedback & asking questions
We welcome feedback and questions! For bugs or feature requests, please use this issue tracker. For ideas or suggestions to discuss, feel free to add a discussion topic here. And for any other questions, join us in the #packit:fedora.im channel on Matrix.
What’s next?
Transition to the new Packit-based CI as the default mechanism, replacing Fedora CI.
This transition will require addressing several technical challenges:
- Deploying the Packit Fedora CI code within the Fedora infrastructure
- Switching Packit Fedora CI to be run on all other Fedora packages
We welcome your feedback. If you’d like to contribute toward reaching our final goal, please add your projects to the list of enabled projects for our Fedora CI here. We’re open to suggestions for improvement and appreciate your support. Thank you!
Recap of the plan
- Phase 1 (Completed): Introduce scratch builds for Fedora dist-git PRs (opt-in).
- Phase 2 (Completed): Implement installability checks (opt-in).
- Phase 3 (Completed): Implement support for user-defined TMT tests (opt-in).
- Final Phase (Next step): Transition to the new Packit-based CI as the default mechanism, replacing Fedora CI.
You can also check our tasklist in this issue.
Final phase targets Fedora Linux 44
The original plan was to do the switch during the Fedora Linux 43 cycle, but most of the Packit team members are temporarily focusing on another project. We promised to provide an actively maintained CI solution for Fedora dist-git, so we would rather postpone the default change by one Fedora cycle to ensure we have the capacity to implement the change properly. However, the current Packit workflows are still supported, including the opt-in approach to Fedora dist-git CI. This means you have more time to try it and provide feedback, and we can deliver a more polished solution when it becomes the default for everyone.
We appreciate your support and look forward to your feedback!
Best, the Packit team