# https://docs.aspect.build/guides/bazelrc/

common --java_language_version=17

common --tool_java_language_version=17

common --java_runtime_version=remotejdk_17

common --tool_java_runtime_version=remotejdk_17

# Do not upload locally executed action results to the remote cache.

# This should be the default for local builds so local builds cannot poison the remote cache.

# It should be flipped to `--remote_upload_local_results` on CI

# by using `--bazelrc=.aspect/bazelrc/ci.bazelrc`.

# Docs: https://bazel.build/reference/command-line-reference#flag--remote_upload_local_results

build --noremote_upload_local_results

# Don't allow network access for build actions in the sandbox.

# Ensures that you don't accidentally make non-hermetic actions/tests which depend on remote

# services.

# Developers should tag targets with `tags=["requires-network"]` to opt-out of the enforcement.

# Docs: https://bazel.build/reference/command-line-reference#flag--sandbox_default_allow_network

build --sandbox_default_allow_network=false

# Warn if a test's timeout is significantly longer than the test's actual execution time.

# Bazel's default for test_timeout is medium (5 min), but most tests should instead be short (1 min).

# While a test's timeout should be set such that it is not flaky, a test that has a highly

# over-generous timeout can hide real problems that crop up unexpectedly.

# For instance, a test that normally executes in a minute or two should not have a timeout of

# ETERNAL or LONG as these are much, much too generous.

# Docs: https://bazel.build/docs/user-manual#test-verbose-timeout-warnings

test --test_verbose_timeout_warnings

# Allow the Bazel server to check directory sources for changes. Ensures that the Bazel server

# notices when a directory changes, if you have a directory listed in the srcs of some target.

# Recommended when using

# [copy_directory](https://github.com/aspect-build/bazel-lib/blob/main/docs/copy_directory.md) and

# [rules_js](https://github.com/aspect-build/rules_js) since npm package are source directories

# inputs to copy_directory actions.

# Docs: https://bazel.build/reference/command-line-reference#flag--host_jvm_args

startup --host_jvm_args=-DBAZEL_TRACK_SOURCE_DIRECTORIES=1

# Allow exclusive tests to run in the sandbox. Fixes a bug where Bazel doesn't enable sandboxing for

# tests with `tags=["exclusive"]`.

# Docs: https://bazel.build/reference/command-line-reference#flag--incompatible_exclusive_test_sandboxed

test --incompatible_exclusive_test_sandboxed

# Use a static value for `PATH` and does not inherit `LD_LIBRARY_PATH`. Doesn't let environment

# variables like `PATH` sneak into the build, which can cause massive cache misses when they change.

# Use `--action_env=ENV_VARIABLE` if you want to inherit specific environment variables from the

# client, but note that doing so can prevent cross-user caching if a shared cache is used.

# Docs: https://bazel.build/reference/command-line-reference#flag--incompatible_strict_action_env

build --incompatible_strict_action_env

# Propagate tags from a target declaration to the actions' execution requirements.

# Ensures that tags applied in your BUILD file, like `tags=["no-remote"]`

# get propagated to actions created by the rule.

# Without this option, you rely on rules authors to manually check the tags you passed

# and apply relevant ones to the actions they create.

# See https://github.com/bazelbuild/bazel/issues/8830 for details.

# Docs: https://bazel.build/reference/command-line-reference#flag--experimental_allow_tags_propagation

build --experimental_allow_tags_propagation

fetch --experimental_allow_tags_propagation

query --experimental_allow_tags_propagation

# Do not automatically create `__init__.py` files in the runfiles of Python targets. Fixes the wrong

# default that comes from Google's internal monorepo by using `__init__.py` to delimit a Python

# package. Precisely, when a `py_binary` or `py_test` target has `legacy_create_init` set to `auto (the

# default), it is treated as false if and only if this flag is set. See

# https://github.com/bazelbuild/bazel/issues/10076.

# Docs: https://bazel.build/reference/command-line-reference#flag--incompatible_default_to_explicit_init_py

build --incompatible_default_to_explicit_init_py

# Set default value of `allow_empty` to `False` in `glob()`. This prevents a common mistake when

# attempting to use `glob()` to match files in a subdirectory that is opaque to the current package

# because it contains a BUILD file. See https://github.com/bazelbuild/bazel/issues/8195.

# Docs: https://bazel.build/reference/command-line-reference#flag--incompatible_disallow_empty_glob

common --incompatible_disallow_empty_glob

# Always download coverage files for tests from the remote cache. By default, coverage files are not

# downloaded on test result cahce hits when --remote_download_minimal is enabled, making it impossible

# to generate a full coverage report.

# Docs: https://bazel.build/reference/command-line-reference#flag--experimental_fetch_all_coverage_outputs

# detching remote cache results

test --experimental_fetch_all_coverage_outputs

# Attempt to build & test every target whose prerequisites were successfully built.

# Docs: https://bazel.build/docs/user-manual#keep-going

build --keep_going

# Output test errors to stderr so users don't have to `cat` or open test failure log files when test

# fail. This makes the log noiser in exchange for reducing the time-to-feedback on test failures for

# users.

# Docs: https://bazel.build/docs/user-manual#test-output

test --test_output=errors

# Show the output files created by builds that requested more than one target. This helps users

# locate the build outputs in more cases

# Docs: https://bazel.build/docs/user-manual#show-result

build --show_result=20

# Bazel picks up host-OS-specific config lines from bazelrc files. For example, if the host OS is

# Linux and you run bazel build, Bazel picks up lines starting with build:linux. Supported OS

# identifiers are `linux`, `macos`, `windows`, `freebsd`, and `openbsd`. Enabling this flag is

# equivalent to using `--config=linux` on Linux, `--config=windows` on Windows, etc.

# Docs: https://bazel.build/reference/command-line-reference#flag--enable_platform_specific_config

common --enable_platform_specific_config

# Output a heap dump if an OOM is thrown during a Bazel invocation

# (including OOMs due to `--experimental_oom_more_eagerly_threshold`).

# The dump will be written to `<output_base>/<invocation_id>.heapdump.hprof`.

# You may need to configure CI to capture this artifact and upload for later use.

# Docs: https://bazel.build/reference/command-line-reference#flag--heap_dump_on_oom

common --heap_dump_on_oom

# Don't apply `--noremote_upload_local_results` and `--noremote_accept_cached` to the disk cache.

# If you have both `--noremote_upload_local_results` and `--disk_cache`, then this fixes a bug where

# Bazel doesn't write to the local disk cache as it treats as a remote cache.

# Docs: https://bazel.build/reference/command-line-reference#flag--incompatible_remote_results_ignore_disk

build --incompatible_remote_results_ignore_disk

# Directories used by sandboxed non-worker execution may be reused to avoid unnecessary setup costs.

# Save time on Sandbox creation and deletion when many of the same kind of action run during the

# build.

# No longer experimental in Bazel 6: https://github.com/bazelbuild/bazel/commit/c1a95501a5611878e5cc43a3cc531f2b9e47835b

# Docs: https://bazel.build/reference/command-line-reference#flag--reuse_sandbox_directories

build --experimental_reuse_sandbox_directories

# Speed up all builds by not checking if external repository files have been modified.

# Docs: https://github.com/bazelbuild/bazel/blob/1af61b21df99edc2fc66939cdf14449c2661f873/src/main/java/com/google/devtools/build/lib/bazel/repository/RepositoryOptions.java#L244

build --noexperimental_check_external_repository_files

fetch --noexperimental_check_external_repository_files

query --noexperimental_check_external_repository_files

# Directories used by sandboxed non-worker execution may be reused to avoid unnecessary setup costs.

# Save time on Sandbox creation and deletion when many of the same kind of action run during the

# build.

# Docs: https://bazel.build/reference/command-line-reference#flag--reuse_sandbox_directories

build --reuse_sandbox_directories

# Avoid this flag being enabled by remote_download_minimal or remote_download_toplevel

# See https://meroton.com/blog/bazel-6-errors-build-without-the-bytes/

build --noexperimental_action_cache_store_output_metadata

# Speed up all builds by not checking if output files have been modified. Lets you make changes to

# the output tree without triggering a build for local debugging. For example, you can modify

# [rules_js](https://github.com/aspect-build/rules_js) 3rd party npm packages in the output tree

# when local debugging.

# Docs: https://github.com/bazelbuild/bazel/blob/1af61b21df99edc2fc66939cdf14449c2661f873/src/main/java/com/google/devtools/build/lib/pkgcache/PackageOptions.java#L185

# NB: This flag is in bazel6.bazelrc as when used in Bazel 7 is has been observed to break

# "build without the bytes" --remote_download_outputs=toplevel. See https://github.com/aspect-build/bazel-lib/pull/711

# for more info.

build --noexperimental_check_output_files

fetch --noexperimental_check_output_files

query --noexperimental_check_output_files