build/bake: add artifact retention days input#250
Open
crazy-max wants to merge 1 commit into
Open
Conversation
Signed-off-by: CrazyMax <1951866+crazy-max@users.noreply.github.com>
crazy-max
force-pushed
the
add-artifact-retention-days
branch
from
93a9e9b to
7c42968
Compare
tonistiigi
approved these changes
Jul 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This adds an
artifact-retention-daysinput to the build and bake reusable workflows so callers can control how long uploaded local build artifacts are retained.The new input defaults to
0, which preserves the current repository default retention behavior. This matters for large artifacts because local build outputs can consume a lot of GitHub artifact storage when they keep the default retention window. Letting callers shorten retention is a practical way to reduce storage pressure and cost for short-lived CI artifacts, while still allowing longer retention when artifacts need to support release, audit, or debugging workflows.