Migration plan from Zuul to Packit as dist-git CI runners

Dear package maintainers currently using Zuul,

Packit as Fedora dist-git CI has recently reached feature-parity with the Zuul CI, and as the first step
in the final phase implementation of the “Packit as dist-git CI” change [1] we are migrating
the current Zuul CI users to packit Fedora CI [2] and disabling the Zuul runners on
src.fedoraproject.org/projects/rpms/* for the time being.

Our plan is to automatically migrate the Zuul dist-git packages on 2026-01-12 (January 12).
Please let us know of any concerns you might have with the migration up until then so we can decide whether
we can go forward with it. We will send another reminder of this as a reply to this announcement one week
before the migration 2026-01-05 (January 5).

After the packages are migrated we will monitor your feedback [3-6] on this migration and decide if we can go ahead
with the Zuul deprecation and disablement or need to resolve any blocking issues first. We could also keep the
Zuul CI temporarily running on a small subset of packages if requested.

We are looking forward to your feedback on this matter.

PS: The migration of the other Zuul jobs that are linked to pagure.io [7] will be addressed at a later
time as these require custom handling and are tied with the forge migration. We do not have a timeline
for this part yet, but we will provide an update as soon as we have a plan for this.

[1]: Change proposal
[2]: Migration PR
[3]: Fedora CI channel
[4]: Packit channel
[5]: Packit issues
[6]: This email and discussion thread
[7]: fedora-project-config

1 Like

Please Folks, by copying a Links use the top menu and take the chain (:chains:) to link a text to the url otherwise we get the message of: Making sure you're not a bot!

Making sure you’re not a bot! #as a link which is not showing the destination

I also fixed a not existent link to src.fp.o :wink:

Thanks for the tips. Was too late on my side and was not operating at full brain-power. Should be more organized now. The src.fp.o was not meant to be a link though, made it a code block instead.

1 Like

Not sure if reminders work in discourse, but might as well try. We plan to move forward with this in 1 week and would still like to gather feedback on this. The current feedback from the mailing list so far:

What has been discussed so far:

  • Limit the initial Zuul disablement to disable all the non-x86_64 scratch builds 1. Current plan for this is 2026-01-12 (January 12), together with the onboarding on the Packit as dist-git CI runner
  • Add the capability for Packit to do eln scratch builds on rawhide PRs (see issue 2 on exact details) and afterwards we could go ahead with the remaining disablement
  • Be able to run the tmt tests as soon as x86_64 builds are finished 3,4. We will try to get it done as soon as possible, but would not be a blocker for the zuul disablement otherwise

Update to this topic, this change :index_pointing_up: is now live. From now on please use the Packit as dist-git CI enrollment process 1. A helper script to enroll users similar to the zuul-config-generator will be made live shortly. Keep an eye out on the enrollment process page 1 for instructions on how to use it.

3 posts were merged into an existing topic: Requesting a tag for fedora-ci?