Disable bazel remote cache on self-hosted runners #12145
+17
−468
Conversation
This file contains 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
Frizi
changed the title
Frizi
added
the
CI: No changelog needed
🧪 Storybook is successfully deployed!📊 Dashboard:
|
hubertp
approved these changes
Jan 25, 2025
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.
Pull Request Description
Bazel cache download is taking significant time on self-hosted github actions runners, pretty much negating any benefit of caching in the first place. Disabling them should speed up many workflows. Since we don't clear the local bazel directory between builds, we still have effective local caching as long as the runners are not recreated.
Additionally removed wasm-pack installation from most jobs, since it is only used in wasm testing target.