Repository navigation
Adopt shared cache retention for CI build caches - #1481
Merged
Merged
Conversation
Use per-run main/PR keys for Bazel and ccache so the shared p4lang/.github retention action can prune stale entries. Scope Bazel restores to the runner image, architecture, and Bazel version. Add scheduled maintenance and a manual dry-run option, pinned to the action revision in p4lang/.github#22 used by PI. Signed-off-by: fruffy <fruffy@nyu.edu>
chreekat
approved these changes
Nov 5, 2026
Signed-off-by: fruffy <fruffy@nyu.edu>
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.
Summary
p4lang/.github/CI/cache-retentionaction in a daily/manual maintenance workflow, with a manual dry-run option. Pin the same implementation revision used by PI (4bec527fd3988345ec240ae8f4f000bc938e4259).ccache-v2-/bazel-v2-keys ending in main/PR scope, run ID, and attempt, as required by the shared retention policy. Successful builds save fresh caches; PRs restore their own compatible cache before falling back to main.Legacy caches and Docker/BuildKit caches are outside the managed prefixes and remain subject to GitHub's normal expiration.
Uses the merged shared action from p4lang/.github#22. Companion adoptions: p4lang/PI#694 and p4lang/p4c#5922.