--incompatible_remote_results_ignore_disk + --disk_cache makes --incompatible_remote_build_event_upload_respect_no_cache not work
#14463
Comments
|
cc @coeuvre |
coeuvre
added a commit
to coeuvre/bazel
that referenced
this issue
Dec 23, 2021
…e working with --incompatible_remote_results_ignore_disk. Fixes bazelbuild#14463. Closes bazelbuild#14468. PiperOrigin-RevId: 417984062
Wyverald
pushed a commit
that referenced
this issue
Dec 23, 2021
* Remote: Don't upload BES referenced blobs to disk cache. Fixes #14435. Closes #14451. PiperOrigin-RevId: 417629899 * Remote: Make `--incompatible_remote_build_event_upload_respect_no_cache` working with alias. Fixes #14456. Closes #14461. PiperOrigin-RevId: 417637635 * Remote: Make --incompatible_remote_build_event_upload_respect_no_cache working with --incompatible_remote_results_ignore_disk. Fixes #14463. Closes #14468. PiperOrigin-RevId: 417984062
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description of the problem / feature request:
When using
--incompatible_remote_results_ignore_disk+--disk_cache,--incompatible_remote_build_event_upload_respect_no_cacheno longer prevents uploads to BES.Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
This will exclude blobs from upload:
$ git clone git@github.com:bazelbuild/rules_apple.git $ cd rules_apple $ env USE_BAZEL_VERSION=3ea70282c5795670070d8cb546cac8aa321d79ce bazelisk build --remote_cache=grpcs://remote.buildbuddy.io --bes_backend=grpcs://remote.buildbuddy.io --bes_results_url=https://app.buildbuddy.io/invocation/ --incompatible_remote_build_event_upload_respect_no_cache --noremote_upload_local_results --disk_cache=/tmp/bazel_disk_cache //examples/iOS/StickersAppWhile this won't:
What operating system are you running Bazel on?
macOS 12.0.1
What's the output of
bazel info release?Bazel built from HEAD to have #14451 in it.
Have you found anything relevant by searching the web?
#14338
The text was updated successfully, but these errors were encountered: