Repository navigation
ci: add refresh-cache dispatch input to rebuild without reading build cache - #222
Merged
Merged
Conversation
ianpittwood
marked this pull request as ready for review
October 21, 2026 15:35
ianpittwood
requested review from
GCRev,
bschwedler,
skyeturriff,
ssinnott and
zachhannum
as code owners
October 21, 2026 15:35
bschwedler
approved these changes
Oct 21, 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
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.
Part of posit-dev/images-shared#847 (epic posit-dev/images-shared#849, eMudhra intermediate CA compromise).
Summary
Adds a
refresh-cachebooleanworkflow_dispatchinput toproduction.ymlandsession.ymland passes it to both sharedbakery-build-native.ymlcalls insession.ymland the one inproduction.yml.Why
Normal builds reuse the cached
apt-get upgradelayer from the BuildKit registry cache, so a rebuild would ship the oldca-certificates.refresh-cache: truerunsbakery build --no-cachewhile keeping--cache-registry: nothing is read from the cache, and fresh layers are still written back, so later scheduled and push builds don't bring back the stale layer. I tested this against a local registry (details in posit-dev/images-shared#850).|| falsekeepsschedule,pushandpull_requestbehavior unchanged, sinceinputs.*is null for those events.Merge order
posit-dev/images-shared#850 is merged and released to
v0.