Repository navigation
ci: install Bazelisk without rewriting home configuration - #20
Merged
Merged
Conversation
Install checksum-pinned Bazelisk in the runner temporary directory instead of setup-bazel, which unconditionally overwrites ~/.bazelrc and forces a shared output base.
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
1 participant
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.
The Bazel setup action overwrites
~/.bazelrcon every run and forces builds into one shared output directory, even when repository caching is disabled. Install Bazelisk directly so CI uses Bazel's normal configuration and workspace-specific output directories.The workflows download Bazelisk 1.29.0 into the runner's temporary directory, verify its pinned SHA-256 checksum, and add it to PATH as
bazel(orbazel.exe). Existing Bazel version selection continues to apply. Removing the action also removes its managed caches; Bazel retains its normal local caches.Verified the release downloads and checksums for Linux x86_64/arm64, macOS x86_64/arm64, and Windows x86_64. Exercised the Linux installer and Bazel launcher locally without modifying the user's
.bazelrc.