Description of the problem / feature request:
When using --incompatible_remote_build_event_upload_respect_no_cache and building an alias, bep-referenced items are uploaded to the remote cache even with --noremote_upload_local_results. When building the aliased target directly they are correctly excluded from upload.
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=5.0.0rc3 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 //examples/iOS/StickersApp
While this won't:
$ echo '
alias(
name = "through_alias",
actual = "//examples/ios/StickersApp",
)' >> BUILD
$ env USE_BAZEL_VERSION=5.0.0rc3 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 //:through_aliasWhat operating system are you running Bazel on?
macOS 12.0.1
What's the output of bazel info release?
release 5.0 rc3
Have you found anything relevant by searching the web?
#14338
Description of the problem / feature request:
When using
--incompatible_remote_build_event_upload_respect_no_cacheand building an alias, bep-referenced items are uploaded to the remote cache even with--noremote_upload_local_results. When building the aliased target directly they are correctly excluded from upload.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=5.0.0rc3 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 //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?release 5.0 rc3
Have you found anything relevant by searching the web?
#14338