5 posts tagged with "configuration"

There are upstream projects that have multiple release streams and, for example, regularly release patch versions for every active minor version. With pull-from-upstream you have been able to follow only the highest stream, but that now changes. By switching Monitoring status of your package from Monitoring to Monitoring all, you enable triggering pull-from-upstream for every released version, not only the highest. This means you can use options such as version_update_mask, upstream_tag_include or upstream_tag_exclude (those require upstream_project_url to be set) to filter a specific release stream you want to follow, or have multiple pull-from-upstream jobs, each matching different releases and targeting different dist-git branches.

After 105 minor releases we are almost ready to announce our first major release, Packit 1.0.0!

Were you annoyed by Packit creating divergent branches in your package's dist-git repository? You'll be happy to know that Packit now supports a new dist_git_branches syntax that enables fast-forwarding commits between branches.

We are happy to announce that support for non-git upstreams in the pull_from_upstream job is here! This enhancement simplifies configuration by removing the need to define upstream_project_url, opening the door for more use cases, while also simplifying the onboarding in general.

Recently, we received multiple contributions from the Strimzi team, specifically Jakub Stejskal and David Kornel, for the functionality of manual triggering of jobs and other related improvements, mostly focusing on the testing UX. We are very happy about these and would like to showcase the results of their awesome contributions.