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

Revisit and stabilize flags used for remote caching/execution #6649

Closed
buchgr opened this issue Nov 10, 2018 · 4 comments
Closed

Revisit and stabilize flags used for remote caching/execution #6649

buchgr opened this issue Nov 10, 2018 · 4 comments
Labels
P2 We'll consider working on this in future. (Assignee optional) stale Issues or PRs that are stale (no activity for 30 days) team-Remote-Exec Issues and PRs for the Execution (Remote) team type: process

Comments

@buchgr
Copy link
Contributor

buchgr commented Nov 10, 2018

No description provided.

@buchgr buchgr added this to the Remote Execution milestone Nov 10, 2018
@buchgr buchgr self-assigned this Nov 10, 2018
@irengrig irengrig added the WIP label Nov 12, 2018
@jin jin added team-Remote-Exec Issues and PRs for the Execution (Remote) team and removed team-Execution labels Jan 14, 2019
@buchgr
Copy link
Contributor Author

buchgr commented Jan 16, 2019

@agoulti and I have a document that needs some polishing before we can share it.

@davido
Copy link
Contributor

davido commented Jan 16, 2019

The question is whether or not this would affect current Bazel users, that rely on disc cache, e.g.: [1]. If yes, we would need a migration path and migration window.

@buchgr buchgr added P1 I'll work on this now. (Assignee required) P2 We'll consider working on this in future. (Assignee optional) type: process and removed P1 I'll work on this now. (Assignee required) labels Jan 21, 2019
@buchgr buchgr removed their assignment Jan 9, 2020
@meisterT meisterT removed this from the Remote Execution milestone May 12, 2020
@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 2.5 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 Mar 16, 2023
@github-actions
Copy link

This issue has been automatically closed due to inactivity. If you're still interested in pursuing this, please reach out to the triage team (@bazelbuild/triage). Thanks!

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P2 We'll consider working on this in future. (Assignee optional) stale Issues or PRs that are stale (no activity for 30 days) team-Remote-Exec Issues and PRs for the Execution (Remote) team type: process
Projects
None yet
Development

No branches or pull requests

5 participants