packit Archives – Fedora Community Blog

Tag: packit

Packit as Fedora dist-git CI: final phase

Hello Fedora Community,

We are back with the final update on the Packit as Fedora dist-git CI change proposal. Our journey to transition Fedora dist-git CI to a Packit-based solution is entering its concluding stage. This final phase marks the transition of Packit-driven CI from an opt-in feature to the default mechanism for all Fedora packages, officially replacing the legacy Fedora CI and Fedora Zuul Tenant on dist-git pull requests.

What we have completed

Over the past several months, we have successfully completed the first three phases of this rollout:

Phase 1: Introduced Koji scratch builds.
Phase 2: Implemented standard installability checks.
Phase 3: Enabled support for user-defined TMT tests via Testing Farm.

Through the opt-in period, we received invaluable feedback from early adopters, allowing us to refine the reporting interface and ensure that re-triggering jobs via PR comments works seamlessly.

Users utilising Zuul CI have been already migrated to using Packit. You can find the details regarding this transition in this discussion thread.

The Final Phase: Transition to Default

We are now moving into the last phase, where we are preparing to switch to the default. After that, you will no longer need to manually add your project to the allowlist. Packit will automatically handle CI for every Fedora package. The tests themselves aren’t changing – Testing Farm still does the heavy lifting.

Timeline & Expectations

Our goal, as previously mentioned, is to complete the switch and enable Packit as the default CI by the end of February 2026. The transition is currently scheduled for February 16, 2026.

To ensure a smooth transition, we are currently working on the final configuration of the system. This includes:

Opt-out mechanism: While Packit will be the default, an opt-out mechanism will be available for packages with specialised requirements. This will be documented at packit.dev/fedora-ci.
Documentation updates: Following the switch, we will also adjust official documentation in other relevant places, such as docs.fedoraproject.org/en-US/ci/, to reflect the new standard.

We will keep you updated via our usual channels in case the target date shifts. You can also check our tasklist in this issue.

How to prepare and provide feedback

You can still opt-in today to test the workflow on your packages and help us catch any edge cases before the final switch.

While we are currently not aware of any user-facing blockers, we encourage you to let us know if you feel there is something we have missed. Our current priority is to provide a matching feature set to the existing solutions. Further enhancements and new features will be discussed and planned once the switch is successfully completed.

Bugs/Feature Requests: Please use our issue tracker.
Discussion: Join the conversation on discussion.fedoraproject.org.
Chat: Reach out to us in the #packit:fedora.im channel on Matrix.

We want to thank everyone who has tested the service so far. Your support is what makes this transition possible!

Best,

the Packit team

Packit as Fedora dist-git CI: Phase 1 completed

March 4, 2025 / Laura Barcziová / Comments Off

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 will be 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.

Source-git SIG report #1

July 1, 2021 / ttomecek / Comments Off

Greetings from the Fedora source-git SIG! We are planning to start publishing reports of what we are working on so everyone can easily pay attention and get involved if interested. If you have any ideas, comments or requests, don’t be shy and let us know 🙂

Here’s a short list of things which we are working on.

Photo by JJ Ying on Unsplash

tmt hints: create a basic test

March 23, 2021 / psss / Comments Off

For those who still haven’t heard: tmt is now fully-supported in Packit, Fedora Continuous Integration (CI) system, and the RHEL CI system. Now you can use the same concise and consistent config to enable tests across all of them, more easily open source tests, share test coverage across releases ,and run tests as early as possible.

In the coming weeks we’ll be sharing short, bite-sized examples demonstrating tmt usage. With these, new users can get started quickly and existing users won’t miss various interesting and useful features hidden under the hood.

Here we go with the first set of examples showing how to quickly enable a simple smoke test for your component, assuming you are in your project git repository:

    sudo dnf install -y tmt
    cd git/fedora/rpms/foo
    tmt init --template mini
    vim plans/example.fmf

Adjust the example plan to run the desired command:

    summary: Basic smoke test
    execute:
        script: foo --version

The very minimal config is really just two lines:

    execute:
        script: make test

Now submit the pull request and wait for the results:

    git add .
    git checkout -b smoke-test
    git commit -m "Enable a simple smoke test"
    git push fork -u smoke-test

Eager to learn more? Not patient enough to wait for the results from the CI pipeline? Willing to safely execute tests from your laptop right now? Check the rest of the first chapter of our brand new guide to learn more.

This is an generic banner that goes with Weekly Updates

GSoC Progress Report: Dashboard for Packit (July 1 – Aug 16 2020)

August 25, 2020 / Anchit / Comments Off

Hi! I am Anchit, and I’m working on the dashboard and the API for Packit Service. If you’d like to know more about me or this project, check out my previous post here.

Using source-git to maintain packages in Fedora

July 21, 2020 / ttomecek / Comments Off

Some time ago, we initiated a discussion on the devel list if dist-git is a good place to work. This thread received a great amount of wonderful feedback from you and we are so grateful for every message—it demonstrates the passion of the Fedora community.

If you are not familiar with how packages are being maintained in Fedora or what dist-git is, let me give you a quick summary. Every Fedora package has a dedicated git repository—a dist-git repository. It contains files needed to compile the sources and produce a binary RPM package which you can install on your Fedora Linux system. As an example, you can look at firefox dist-git repository.

This blog post is a followup to the discussion and lays out a concrete plan of what we want to do.

GSoC Progress Report: Dashboard for Packit

June 30, 2020 / Anchit / Comments Off

About Me

Hi, I am Anchit, a 19 y.o. from Chandigarh, India. I love programming, self-hosting, gaming, reading comic books, and watching comic-book based movies/tv.

The first version of Fedora I tried was 21 when I came across it during my distro-hopping spree. I used it for a couple of months and then moved on to other distros. I came back to Fedora in 2017 after a couple of people on Telegram recommended it and have been using it ever since. A big reason why I stuck with Fedora this time is the community. Shout out to @fedora on Telegram. They’re nice, wholesome and helpful. They also got me into self-hosting and basic sys-admin stuff.