Repository navigation
workflows: retry transient Bazel download failures in setup-bazel - #4291
Merged
rickeylev merged 2 commits intoOct 20, 2026
Merged
Conversation
`bazel-contrib/setup-bazel` configures Bazelisk and restores caches, leaving the Bazel binary download to the first `bazel` invocation. Bazelisk retries initial HTTP GET headers, but does not retry mid-stream `io.Copy` failures (such as HTTP/2 stream resets from `releases.bazel.build`). A failed download also leaves an empty `~/.cache/bazelisk` directory that `setup-bazel`'s post step caches. To prevent transient network flakes, pin Bazelisk to 1.29.0 (for `windows-arm64` support) in the shared `setup-bazel` composite action, eagerly run `bazel --version` with exponential-backoff retries, delete partial Bazelisk cache directories if all retries fail, and reuse the shared action in the release artifact build workflow.
…work_downloads # Conflicts: # .github/workflows/release_build_artifacts.yaml
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.
bazel-contrib/setup-bazelconfigures Bazelisk and restores caches,leaving the Bazel binary download to the first
bazelinvocation.Bazelisk retries initial HTTP GET headers, but does not retry
mid-stream
io.Copyfailures (such as HTTP/2 stream resets fromreleases.bazel.build). A failed download also leaves an empty~/.cache/bazeliskdirectory thatsetup-bazel's post step caches.To prevent transient network flakes, pin Bazelisk to 1.29.0 (for
windows-arm64support) in the sharedsetup-bazelcomposite action,eagerly run
bazel --versionwith exponential-backoff retries, deletepartial Bazelisk cache directories if all retries fail, and reuse the
shared action in the release artifact build workflow.