Skip to main content

5 posts tagged with "propose-downstream"

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
Laura Barcziová

In the upcoming months, we plan to migrate our service to a new cluster. However, this may affect propose_downstream and pull_from_upstream jobs due to the new firewall rules. The problematic aspects could be:

  • commands you run in your actions during syncing the release involving interactions with external servers
  • downloading your sources from various hosting services (crates.io, npm, gems, etc.)

To smoothen this transition, we kindly encourage you to enable one of these jobs on our already migrated staging instance. This recommendation is particularly important if you belong to one of the groups affected by the two previous points. This proactive step will help us identify and address any issues promptly.