FR: Add a `--remote_upload_mode` that mirrors the behavior of `--bes_upload_mode`
- Dominant language
- Java
- Stars
- 25.8k
- Forks
- 4.6k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 75
Description
### Description of the problem / feature request:
With the introduction of `--experimental_remote_cache_async`, it's now possible to have to wait at the end of a build for uploads to complete. Similar to uploading for BES, the user might not care that uploads are finished yet before wanting to run another command/build. Just as BES has `--bes_upload_mode`, the remote cache should have `--remote_upload_mode`.
### Feature requests: what underlying problem are you trying to solve with this feature?
I want the ability for bazel to continue to upload the outputs of local actions in the background, after a bazel command completes. This can speed up certain workflows.
### What's the output of `bazel info release`?
release 5.0
### Have you found anything relevant by searching the web?
- https://github.com/bazelbuild/bazel/pull/13655#issuecomment-1021149626
- https://github.com/bazelbuild/bazel/pull/14634
Contributor guide
Research direction
Start by tracing the existing --bes_upload_mode implementation and the --experimental_remote_cache_async upload path; the issue does not name specific files or tests. The work is done when --remote_upload_mode provides equivalent background-upload behavior for remote cache outputs and its command-line behavior is covered by the relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100