Skip to content

ci: set 1-day retention for intermediate image artifacts - #5

Merged
pbalogh-sa merged 1 commit into
mainfrom
ci/artifact-retention-1day
Jul 22, 2026
Merged

ci: set 1-day retention for intermediate image artifacts#5
pbalogh-sa merged 1 commit into
mainfrom
ci/artifact-retention-1day

Conversation

@pbalogh-sa

Copy link
Copy Markdown
Member

Summary

docker.yml uploads per-arch image tarballs (image-<arch>.tar) as GitHub Actions artifacts. These are purely intermediate hand-offs: the build-image job produces them and the downstream push-manifest job consumes them within the same run to load/push images and assemble the multi-arch manifest.

Without an explicit retention-days, they fall back to the repo/org default (up to 90 days), needlessly retaining large image tarballs.

Changes

  • docker.yml — add retention-days: 1 to the image-<arch> upload

Since the artifacts are consumed within the same workflow run, a 1-day retention is safe.

The per-arch docker image tarballs uploaded by the build-image job are
only consumed by the push-manifest job within the same run. Without an
explicit retention-days they fall back to the default (up to 90 days),
needlessly retaining large image tarballs. Set retention-days: 1.

Signed-off-by: Peter Balogh <poke@riptides.io>
@pbalogh-sa
pbalogh-sa requested a review from a team as a code owner July 22, 2026 09:48
@pbalogh-sa
pbalogh-sa merged commit 65a72b1 into main Jul 22, 2026
3 checks passed
@pbalogh-sa
pbalogh-sa deleted the ci/artifact-retention-1day branch July 22, 2026 10:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants