Skip to content

Document gotchas with sources generated in actions during sync_release - #1180

Open
Nitjsefnie wants to merge 1 commit into
packit:mainfrom
Nitjsefnie-OSC:docs/911-generated-sources-sync-release
Open

Nitjsefnie wants to merge 1 commit into
packit:mainfrom
Nitjsefnie-OSC:docs/911-generated-sources-sync-release

Conversation

@Nitjsefnie

@Nitjsefnie Nitjsefnie commented Oct 22, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Document the gotcha that actions generating sources during release syncing run once per target dist-git branch: a non-reproducible generator produces a different archive hash on each run, so the archive is uploaded to the lookaside cache again for every branch. The new note recommends making generation reproducible — Packit already checks the lookaside cache by content hash before uploading, so byte-identical archives are not uploaded again.

Related Issues and Pull Requests

Fixes #911

Changes

  • docs/configuration/examples.md: a note under "Custom archive creation for release syncing" explaining that post-upstream-clone and pre-sync run once per target branch processed by the release-sync loop, that non-reproducible generation (changing timestamps, randomness) changes the archive hash per run and triggers another lookaside upload per branch, and that reproducible generation lets Packit's existing content-hash lookaside check skip the re-upload.

Testing

Docs-only change; nothing was executed locally. Fork CI green on the branch head 57b79c1: osc-manual.yml run 39831010060 on the fork, 1 job green, provenance echo naming that SHA. Upstream CI on this PR: Test deployment green (run 39831664445), zuul packit-service/check success, pre-commit.ci pass.

Footer

Generated by GLM-5.3-Flash (brief, orchestration), GPT-6.1 Sol (research, implementation, review), GPT-6 Astra (review)

…ncing

Co-Authored-By: GPT-6.1 Sol <noreply@openai.com>
@centosinfra-prod-github-app

Copy link
Copy Markdown
Contributor

@Nitjsefnie

Copy link
Copy Markdown
Contributor Author

Heads-up: this branch lives in an organization-owned fork, and GitHub doesn't let maintainers push to those. If anything needs changing, just say so here and I'll make the change on this branch right away.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Development

Successfully merging this pull request may close these issues.

Document gotchas with sources generated in actions during sync_release

2 participants