Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FR: Add a --remote_upload_mode that mirrors the behavior of --bes_upload_mode #14638

Open
brentleyjones opened this issue Jan 25, 2022 · 3 comments
Labels
not stale Issues or PRs that are inactive but not considered stale P2 We'll consider working on this in future. (Assignee optional) team-Remote-Exec Issues and PRs for the Execution (Remote) team type: feature request

Comments

@brentleyjones
Copy link
Contributor

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?

@coeuvre coeuvre added team-Remote-Exec Issues and PRs for the Execution (Remote) team P2 We'll consider working on this in future. (Assignee optional) type: feature request labels Jan 26, 2022
@github-actions
Copy link

Thank you for contributing to the Bazel repository! This issue has been marked as stale since it has not had any activity in the last 1+ years. It will be closed in the next 14 days unless any other activity occurs or one of the following labels is added: "not stale", "awaiting-bazeler". Please reach out to the triage team (@bazelbuild/triage) if you think this issue is still relevant or you are interested in getting the issue resolved.

@github-actions github-actions bot added the stale Issues or PRs that are stale (no activity for 30 days) label Jun 14, 2023
@brentleyjones
Copy link
Contributor Author

@coeuvre I think this is still a valid FR, right?

@coeuvre
Copy link
Member

coeuvre commented Jun 15, 2023

Yes. Not stale.

@coeuvre coeuvre added not stale Issues or PRs that are inactive but not considered stale and removed stale Issues or PRs that are stale (no activity for 30 days) labels Jun 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
not stale Issues or PRs that are inactive but not considered stale P2 We'll consider working on this in future. (Assignee optional) team-Remote-Exec Issues and PRs for the Execution (Remote) team type: feature request
Projects
None yet
Development

No branches or pull requests

2 participants