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

Docs should mention the new no-remote-cache-upload tag #15965

Merged
merged 1 commit into from
Jul 25, 2022
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -42,10 +42,13 @@
executed remotely (but it may be cached remotely).
</li>

<li><code>no-remote</code> keyword prevents the action or test from being executed remotely
or cached remotely. This is equivalent to using both no-remote-cache and no-remote-exec.
<li><code>no-remote</code> keyword prevents the action or test from being executed remotely or
cached remotely. This is equivalent to using both
<code>no-remote-cache</code> and <code>no-remote-exec</code>.
</li>
<li><code>no-remote-cache-upload</code> keyword disables upload part of remote caching of a spawn.
it does not disable remote execution.
</li>

<li><code>local</code> keyword precludes the action or test from being remotely cached,
remotely executed, or run inside the sandbox.
For genrules and tests, marking the rule with the <code>local = True</code>
Expand Down