Thanks for your interest in Packit Service! In order to start using the service you need to be whitelisted, which is an action to be done by us. Once we put you on the whitelist, we’ll get in touch with you. We are now on-boarding Fedora contributors (with a Fedora Account System account).
Since packit service builds your PRs in Fedora COPR build service, by using Packit-as-a-service, your software needs to comply with COPR rules. If any of these points are violated, we’ll remove the builds and may put you on a blacklist so you won’t be able to use the service again.
We are working on simplifying the
.packit.yaml so it’s as small as possible.
We will also handle all potentially backward incompatible changes of
Spec file can be downloaded (see specific question below) from Fedora Pagure instead of having it included in the upstream repository.
Packit makes it trivial to run your project as part of an OS. It provides feedback to your project at the time when the changes are being developed so you can fix incompatible code when you are working on it, not when it’s already released. When you push commits to a pull request, you’ll get RPM build and test results right away.
We’ve started with Fedora Linux because we work for Red Hat and we ❤ Fedora.
Packit service is closely tied to GitHub right now because most of the projects are hosted on GitHub. Let us know if you’d like to see Gitlab support.
If you do not want to have the RPM spec file in your upstream repository, you can download it in actions section.
Add actions section to your packit.yaml configuration file and
download the spec file in a hook
Packit service has a limited set of commands available so please use
The configuration file with downloading the RPM spec file now looks like this:
specfile_path: packit.spec synced_files: - packit.spec - .packit.yaml upstream_package_name: packitos downstream_package_name: packit actions: post-upstream-clone: "wget https://src.fedoraproject.org/rpms/packit/raw/master/f/packit.spec"
The solution is, again, actions and hooks. Just render the spec after the upstream repo is cloned:
specfile_path: my-project.spec upstream_package_name: my-project-src downstream_package_name: my-project actions: post-upstream-clone: "make generate-spec"
Where the “generate-spec” make target could look like this:
generate-spec: sed -e 's/@@VERSION@@/$(VERSION)/g' my-project.spec.template >my-project.spec
As a practical example, cockpit-podman project is using this functionality.
Yes, you can! It’s very simple, just add
centos-stream-x86_64 as a target for
jobs: - job: copr_build trigger: pull_request metadata: targets: - centos-stream-x86_64
If you encounter this error when running tests via Testing Farm, it means you forgot to initialize the metadata tree with
fmf init and include the
.fmf directory in the pull request. See Testing Farm documentation for more information.