Add option to continue with local execution if remote cache is unavailable. #27846
Conversation
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
available at the start of the build. Currently, if the endpoint specified by `--remote_cache` is not available at the start of the build, the build fails with a message saying that the remote cache is not available. This change introduces a new flag `--incompatible_remote_local_fallback_for_remote_cache`, which when combined with `--remote_local_fallback`, allow build to continue build even if the remote cache is not available initially.
Member
Author
|
@bazel-io fork 9.0.0 |
tjgq
requested changes
Dec 11, 2025
src/main/java/com/google/devtools/build/lib/remote/RemoteSpawnCache.java
Show resolved
Hide resolved
tjgq
requested changes
Dec 11, 2025
src/main/java/com/google/devtools/build/lib/remote/options/RemoteOptions.java
Show resolved
Hide resolved
tjgq
approved these changes
Dec 11, 2025
Contributor
|
Are we planning to release 8.4.3 or 8.5.1 to include this? So we don't need to wait for 8.6.0 |
bazel-io
pushed a commit
to bazel-io/bazel
that referenced
this pull request
Dec 15, 2025
…lable. Currently, if the endpoint specified by `--remote_cache` is not available at the start of the build, the build fails with a message saying that the remote cache is not available. This change introduces a new flag `--incompatible_remote_local_fallback_for_remote_cache`, which when combined with `--remote_local_fallback`, allow build to continue build even if the remote cache is not available initially. Fixes bazelbuild#27734, bazelbuild#25965. Closes bazelbuild#27846. PiperOrigin-RevId: 844783391 Change-Id: Id414458b27c2673318ac9767d07bd54887a74e45
linzhp
pushed a commit
to linzhp/bazel
that referenced
this pull request
Dec 15, 2025
…lable. Currently, if the endpoint specified by `--remote_cache` is not available at the start of the build, the build fails with a message saying that the remote cache is not available. This change introduces a new flag `--incompatible_remote_local_fallback_for_remote_cache`, which when combined with `--remote_local_fallback`, allow build to continue build even if the remote cache is not available initially. Fixes bazelbuild#27734, bazelbuild#25965. Closes bazelbuild#27846. PiperOrigin-RevId: 844783391 Change-Id: Id414458b27c2673318ac9767d07bd54887a74e45
Member
|
@bazel-io fork 8.6.0 |
bazel-io
pushed a commit
to bazel-io/bazel
that referenced
this pull request
Dec 15, 2025
…lable. Currently, if the endpoint specified by `--remote_cache` is not available at the start of the build, the build fails with a message saying that the remote cache is not available. This change introduces a new flag `--incompatible_remote_local_fallback_for_remote_cache`, which when combined with `--remote_local_fallback`, allow build to continue build even if the remote cache is not available initially. Fixes bazelbuild#27734, bazelbuild#25965. Closes bazelbuild#27846. PiperOrigin-RevId: 844783391 Change-Id: Id414458b27c2673318ac9767d07bd54887a74e45
github-merge-queue bot
pushed a commit
that referenced
this pull request
Dec 18, 2025
…s unavailable. (#28001) Currently, if the endpoint specified by `--remote_cache` is not available at the start of the build, the build fails with a message saying that the remote cache is not available. This change introduces a new flag `--incompatible_remote_local_fallback_for_remote_cache`, which when combined with `--remote_local_fallback`, allow build to continue build even if the remote cache is not available initially. Fixes #27734, #25965. Closes #27846. PiperOrigin-RevId: 844783391 Change-Id: Id414458b27c2673318ac9767d07bd54887a74e45 Commit 461c074 Co-authored-by: Chi Wang <coeuvre@gmail.com>
github-merge-queue bot
pushed a commit
that referenced
this pull request
Dec 18, 2025
…s unavailable. (#27990) Currently, if the endpoint specified by `--remote_cache` is not available at the start of the build, the build fails with a message saying that the remote cache is not available. This change introduces a new flag `--incompatible_remote_local_fallback_for_remote_cache`, which when combined with `--remote_local_fallback`, allow build to continue build even if the remote cache is not available initially. Fixes #27734, #25965. Closes #27846. PiperOrigin-RevId: 844783391 Change-Id: Id414458b27c2673318ac9767d07bd54887a74e45 Commit 461c074 Co-authored-by: Chi Wang <coeuvre@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
Currently, if the endpoint specified by
--remote_cacheis not available at the start of the build, the build fails with a message saying that the remote cache is not available.This change introduces a new flag
--incompatible_remote_local_fallback_for_remote_cache, which when combined with--remote_local_fallback, allow build to continue build even if the remote cache is not available initially.Fixes #27734, #25965.