Conversation
- Upgrade bazel-contrib/setup-bazel to v0.18.0 - Set cache-save to only write on push events to prevent pull requests from polluting the Bazel cache - Disable caching for copyright and format as it doesn't bring much for these simple workflows, but polutes github cache
By introducing a parameter, workflows can now pass a custom string to use as cache key for workflow separation.
Member
Author
|
The changes are tested with eclipse-score/baselibs#84 |
FScholPer
approved these changes
Jan 28, 2026
github-project-automation
bot
moved this from Draft
to Done
in INF - Infrastructure Community
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 PR improves Bazel caching behavior across the workflows:
bazel-contrib/setup-bazeltov0.18.0.bazel-contrib/setup-bazelis very coarse, and saving the cache from such workflows would just make other workflows not benefiting from Bazel cache either.bazel-disk-cacheinput to the QNX workflow so callers can supply a custom cache key (string) to separate caches per workflow/target. The hope is to make the caching is a bit more useful. Unfortunately it's not possible to modify the cache key for repository cache. The issues insetup-bazelare discussed in Update disk cache on cache hits bazel-contrib/setup-bazel#18 and Should all caches, not just disk-cache, take custom keys? (or one universal key for all caches) bazel-contrib/setup-bazel#73