diff --git a/docs/configuration/examples.md b/docs/configuration/examples.md index 9fc50d84d3..0c7dbee24c 100644 --- a/docs/configuration/examples.md +++ b/docs/configuration/examples.md @@ -114,6 +114,22 @@ to place the commands necessary for the creation. You also have to include the a be moved to the dist-git repo so that it is then handled by Packit from there. **Note:** Beware of how Packit uploads files to lookaside cache or adds them to dist-git (see [this note][files_to_sync_info] for more details). +**Note:** During `propose-downstream` / `pull-from-upstream`, the configured `post-upstream-clone` +and `pre-sync` actions run once per target dist-git branch processed by the release-sync loop +(when reached), not once per invocation. A non-reproducible generator (e.g. including changing +timestamps or randomness) can therefore produce a different archive hash on each run, triggering +another upload for each branch when that content is absent from the lookaside cache and uploads +are enabled. Make your generation reproducible: identical inputs should produce byte-identical +archives. If that is not possible, have the action check Fedora's lookaside cache for the archive by +name and, if present, download an appropriate copy instead of generating it again. The cache lists +each package's files at `https://src.fedoraproject.org/repo/pkgs//`; when configured, the +package name is available in `PACKIT_DOWNSTREAM_PACKAGE_NAME`. When handling sources, Packit still +runs the upload step if an archive's filename does not occur in the branch's `sources` file, but +fedpkg/centpkg do not upload a file whose name and hash are already in the cache for the same package. +Packit skips the upload step entirely only when all archives already exist in the cache for the same +package and filenames, their filenames occur in the branch's `sources` file, and `--force-new-sources` +is not set. +
Creating an archive using tito and syncing it to dist-git repo