Lines Matching +full:bazel +full:- +full:cache

1 # Copyright 2022 The Bazel Authors. All rights reserved.
7 #    http://www.apache.org/licenses/LICENSE-2.0
17 # Hints for Bazel spawn strategy
19     # ----------------+-----------------------------------------------------------------------------
20     # no-remote       | Prevents the action or test from being executed remotely or cached remotely.
21     #                 | This is equivalent to using both `no-remote-cache` and `no-remote-exec`.
22     # ----------------+-----------------------------------------------------------------------------
23     # no-cache        | Results in the action or test never being cached (remotely or locally)
24     # ----------------+-----------------------------------------------------------------------------
25     # See https://bazel.build/reference/be/common-definitions#common-attributes
27     # Copying file & directories is entirely IO-bound and there is no point doing this work
30     # Also, remote-execution does not allow source directory inputs, see
31     # https://github.com/bazelbuild/bazel/commit/c64421bc35214f0414e4f4226cc953e8c55fa0d2 So we must
34     # There is also no point pulling the output file or directory from the remote cache since the
35     # bytes to copy are already available locally. Conversely, no point in writing to the cache if
38     # Read and writing to disk cache is disabled as well primarily to reduce disk usage on the local
39     # machine. A disk cache hit of a directory copy could be slghtly faster than a copy since the
40     # disk cache stores the directory artifact as a single entry, but the slight performance bump
41     # comes at the cost of heavy disk cache usage, which is an unmanaged directory that grow beyond
43     "no-remote": "1",
44     "no-cache": "1",