Skip to main content

6 posts tagged with "configuration"

View All Tags

· 9 min read
Nikola Forró

In Packit, release synchronization is the process of landing an upstream release in a dist-git repo. Let's take a look at how the process works under the hood and how you can customize it.

First, let me define some terms:

  • propose_downstream - release sync job triggered by an upstream release, configured upstream
  • pull_from_upstream - release sync job triggered by a release-monitoring.org event, configured in dist-git
  • action - list of commands that can replace the default Packit implementation of a certain step of the process
  • hook - action that does nothing by default
  • source - source defined in the spec file, either as a Source/SourceN tag or as a %sourcelist entry
  • remote source - source defined as a URL

· 2 min read
Nikola Forró

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.