| 1 |
# Directories used by sandboxed non-worker execution may be reused to avoid unnecessary setup costs. |
| 2 |
# Save time on Sandbox creation and deletion when many of the same kind of action run during the |
| 3 |
# build. |
| 4 |
# No longer experimental in Bazel 6: https://github.com/bazelbuild/bazel/commit/c1a95501a5611878e5cc43a3cc531f2b9e47835b |
| 5 |
# Docs: https://bazel.build/reference/command-line-reference#flag--reuse_sandbox_directories |
| 6 |
build --experimental_reuse_sandbox_directories |
| 7 |
|
| 8 |
# Avoid creating a runfiles tree for binaries or tests until it is needed. |
| 9 |
# Docs: https://bazel.build/reference/command-line-reference#flag--build_runfile_links |
| 10 |
# See https://github.com/bazelbuild/bazel/issues/6627 |
| 11 |
# |
| 12 |
# This may break local workflows that `build` a binary target, then run the resulting program |
| 13 |
# outside of `bazel run`. In those cases, the script will need to call |
| 14 |
# `bazel build --build_runfile_links //my/binary:target` and then execute the resulting program. |
| 15 |
build --nobuild_runfile_links |
| 16 |
|
| 17 |
# Needed prior to Bazel 8; see |
| 18 |
# https://github.com/bazelbuild/bazel/issues/20577 |
| 19 |
coverage --build_runfile_links |