Packit Service

Packit Service #

Helps you continuously ensure that your project works in Fedora Linux or CentOS Stream.

Easy to use #

Using Packit Service is very straightforward: add one config file to your repository together with the RPM spec file.

On Github you also need to install (see below) our Github App, for Gitlab see FAQ.

Packit Service validates your pull requests by building your software in Fedora OS. Once the builds are done, Packit lets you know how to install the RPMs inside your environment so you can try the changes before merging them.

Optionally, Packit Service can run tests for the built software (i.e. copr builds) in all current Fedora OS releases via Testing Farm.

Packit is also available as a CLI tool, so you can always try things locally on your own. Note that testing is not currently supported with the CLI tool.

Requirements for running Packit Service jobs #

As a first step, you need to have a valid Fedora Account System account to be approved by us and start using Packit Service. Besides that:

  • If you want to configure builds via Packit Service, your software needs to comply with Copr guidelines since we use Fedora Copr for the builds. Therefore, please, make sure you read them before configuring the Packit Service build job.
  • If you are interested in using internal instance of the Testing Farm to run your tests in, please, reach out to us, since for this job, an additional approval on our side is needed.
  • For retrying the build and test jobs via /packit build and /packit test pull request comments, you need to have write access to the repository or be the author of the pull request.
  • Similarly, for retrying the propose downstream job via /packit propose-downstream issue comment, you need to have write access to the repository.

Integrating Packit-as-a-Service into your project or organization from GitHub Marketplace #

  1. Navigate to the “Packit-as-a-Service” GitHub application.
  2. Under “Pricing and setup”, click “Install it for free”.
  3. Click “Complete order and begin installation”.
  4. Install the “Packit-as-a-Service” to repositories of your choice.

Once installed, you will see the “Packit-as-a-Service” GitHub application in your project settings. In the left sidebar, click “Integration & services” and you will see the application displayed there.

In order to continue, please head to the main Packit guide.

Staging instance #

Packit-as-a-Service-stg GitHub App runs the latest code. It can be used to verify latest changes until they get (every Tuesday) into the prod instance. See more details.

How to check Packit Service works in your project? #

Currently, Packit Service is able only to build your changes and provide them as RPMs. Once you create a pull request, Packit Service builds the code from the pull request in COPR repository and reports back COPR build status to the pull request.

An example of Packit Service pull request:

Packit service pull request

How to re-trigger Packit Service actions in your pull request? #

Packit Service is able to schedule new builds based on a pull request comment:

/packit copr-build

or the shorter version

/packit build

So whenever you run into a flake or feel like you want to retrigger, just type that comment into the PR and enjoy some fine, fresh builds.

The requirements stated in the previous section apply, so if you see this message

Only users with write or admin permissions to the repository can trigger
Packit-as-a-Service

it means the author of the pull request does not have write access to the repository so the build cannot be scheduled. This is a perfect case for maintainers of the repository to post /packit build in the PR to get a build.

In Github Checks interface, it is also possible to re-trigger a specific task just by clicking on Re-run for the particular check:

Re-run Github check

Or it is possible to re-trigger every failed task using a pull request comment

/packit rebuild-failed

which builds only failed builds and similar for testing farm

/packit retest-failed

to re-trigger every failed test.

How to propose a new downstream update? #

Packit Service is able to propose updates of new upstream releases using this comment in an issue:

/packit propose-downstream

If you want to propose the latest release into Fedora repositories, create an issue and add that comment into this issue and Packit service triggers and pushes it directly into Fedora dist-git repositories.

If all jobs (propose_downstream, defined in packit.yaml file, finished successfully, then the issue is automatically closed.

Only users with write or admin permissions to the repository can propose a new update.

Adding tests #

It is also possible to run tests against the freshly built rpms. See the Testing Farm documentation for details.