-
Notifications
You must be signed in to change notification settings - Fork 187
copy_file should *never* set no-remote
#562
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
Comments
There also won't be a new CAS entry, so this would virtually be all upside. RBE does support source directories now. That said, ideally |
If I read the code correctly, |
@ulfjack I think that's not true, |
You're right. Apparently I misread the code. I agree that it should default to true. |
When build-without-the-bytes is used, forcing
no-remote
+no-cache
is often worse than allowing it to execute remotely. If the file is a source file, then it's better to upload it right away and execute the copy remotely (cached). If the file is an output file, then Bazel has to download the file in order to perform a local copy. Best case scenario, no work is ever done locally, and this breaks that.It's a better policy to not try to set these at the rule level.
If this needs to be user-configurable on a per-rule basis, it might be viable to create a flag and then set these tags only if the flag is set.
The text was updated successfully, but these errors were encountered: