Specifies the set of environment variables available to actions. Variables can be either specified by name, in which case the value will be taken from the invocation environment, or by the name=value pair which sets the value independent of the invocation environment. This option can be used multiple times; for options given for the same variable, the latest wins, options for different variables accumulate.

adb binary to use for the 'mobile-install' command. If unspecified, the one in the Android SDK specified by the --android_sdk command line option (or the default SDK if --android_sdk is not specified) is used.

Extra arguments to pass to adb. Usually used to designate a device to install to.

Enables all options of the form --incompatible_*. Use this option to find places where your build may break in the future due to deprecations or other changes. Expands to: --incompatible_allow_python_version_transitions -- incompatible_auto_configure_host_platform -- incompatible_bzl_disallow_load_after_statement --incompatible_cc_coverage --incompatible_depset_is_not_iterable --incompatible_depset_union -- incompatible_disable_cc_configuration_make_variables -- incompatible_disable_cc_toolchain_label_from_crosstool_proto -- incompatible_disable_crosstool_file -- incompatible_disable_deprecated_attr_params -- incompatible_disable_depset_in_cc_user_flags -- incompatible_disable_expand_if_all_available_in_flag_set -- incompatible_disable_genrule_cc_toolchain_dependency -- incompatible_disable_late_bound_option_defaults -- incompatible_disable_legacy_cc_provider -- incompatible_disable_legacy_cpp_toolchain_skylark_api -- incompatible_disable_legacy_crosstool_fields -- incompatible_disable_legacy_flags_cc_toolchain_api -- incompatible_disable_legacy_proto_provider -- incompatible_disable_objc_library_resources -- incompatible_disable_objc_provider_resources -- incompatible_disable_proto_source_root -- incompatible_disable_runtimes_filegroups -- incompatible_disable_sysroot_from_configuration -- incompatible_disable_third_party_license_checking -- incompatible_disable_tools_defaults_package -- incompatible_disallow_data_transition --incompatible_disallow_dict_plus -- incompatible_disallow_filetype -- incompatible_disallow_legacy_java_provider -- incompatible_disallow_legacy_javainfo -- incompatible_disallow_legacy_py_provider -- incompatible_disallow_load_labels_to_cross_package_boundaries -- incompatible_disallow_native_in_build_file -- incompatible_disallow_old_style_args_add -- incompatible_disallow_resource_jars -- incompatible_disallow_struct_provider_syntax -- incompatible_dont_emit_static_libgcc -- incompatible_dont_enable_host_nonhost_crosstool_features -- incompatible_enable_cc_toolchain_resolution -- incompatible_enable_legacy_cpp_toolchain_skylark_api -- incompatible_expand_directories --incompatible_java_coverage -- incompatible_linkopts_in_user_link_flags -- incompatible_list_based_execution_strategy_selection -- incompatible_merge_genfiles_directory --incompatible_new_actions_api -- incompatible_no_attr_license --incompatible_no_output_attr_default -- incompatible_no_support_tools_in_action_inputs -- incompatible_no_target_output_group --incompatible_no_transitive_loads -- incompatible_provide_cc_toolchain_info_from_cc_toolchain_suite -- incompatible_py2_outputs_are_suffixed --incompatible_py3_is_default -- incompatible_remap_main_repo --incompatible_remote_symlinks -- incompatible_remove_cpu_and_compiler_attributes_from_cc_toolchain -- incompatible_remove_legacy_whole_archive -- incompatible_remove_native_maven_jar -- incompatible_remove_old_python_version_api -- incompatible_require_feature_configuration_for_pic -- incompatible_require_java_toolchain_header_compiler_direct -- incompatible_strict_action_env --incompatible_strict_argument_ordering -- incompatible_strict_objc_module_maps -- incompatible_symlinked_sandbox_expands_tree_artifacts_in_runfiles_tree -- incompatible_use_aapt2_by_default -- incompatible_use_jdk10_as_host_javabase -- incompatible_use_jdk11_as_host_javabase -- incompatible_use_remote_host_java_toolchain -- incompatible_use_remote_java_toolchain -- incompatible_use_toolchain_providers_in_java_common -- incompatible_windows_escape_jvm_flags

If true, an analysis failure of a rule target results in the target's propagation of an instance of AnalysisFailureInfo containing the error description, instead of resulting in a build failure.

Sets the maximum number of transitive dependencies through a rule attribute with a for_analysis_testing configuration transition. Exceeding this limit will result in a rule error.

Selects the version of androidAaptVersion to use for android_binary rules. Flag to help the test and transition to aapt2.

The Android target compiler.

The Android target CPU.

The location of the C++ compiler used for Android builds.

Use android databinding v2 with 3.4.0 argument

Determines whether C++ deps of Android rules will be linked dynamically when a cc_binary does not explicitly create a shared library. 'default' means bazel will choose whether to link dynamically. 'fully' means all libraries will be linked dynamically. 'off' means that all libraries will be linked in mostly static mode.

The Android target grte_top.

Selects the manifest merger to use for android_binary rules. Flag to help thetransition to the Android manifest merger from the legacy merger.

Sets the order of manifests passed to the manifest merger for Android binaries. ALPHABETICAL means manifests are sorted by path relative to the execroot. ALPHABETICAL_BY_CONFIGURATION means manifests are sorted by paths relative to the configuration directory within the output directory. DEPENDENCY means manifests are ordered with each library's manifest coming before the manifests of its dependencies.

Enables resource shrinking for android_binary APKs that use ProGuard.

Specifies Android SDK/platform that is used to build Android applications.

Deprecated. No-op.

Whether to announce rc options.

Implementation to use to sign APKs

Specify the Apple bitcode mode for compile steps. Values: 'none', 'embedded_markers', 'embedded'.

The Apple target compiler. Useful for selecting variants of a toolchain (e. g. xcode-beta).

The label of the crosstool package to be used in Apple and Objc rules and their dependencies.

Whether to force enable generating debug symbol(.dSYM) file(s) for dbg builds.

Whether to generate debug symbol(.dSYM) file(s).

The Apple target grte_top.

Location of target that will provide the appropriate Apple SDK for the current build configuration.

Comma-separated list of aspects to be applied to top-level targets. All aspects are applied to all top-level targets independently. Aspects are specified in the form <bzl-file-label>%<aspect_name>, for example '//tools:my_def.bzl%my_aspect', where 'my_aspect' is a top-level value from from a file tools/my_def.bzl

When printing the location part of messages, attempt to use a path relative to the workspace directory or one of the directories specified by -- package_path.

Declare the environment_group to use for automatically mapping cpu values to target_environment values.

When set we collect and publish used_heap_size_post_build from build_event_stream.proto. This forces a full GC and is off by default.

Specifies the build event service (BES) backend endpoint as HOST or HOST: PORT. Disabled by default.

BES best effort upload has been removed. The flag has no more functionality attached to it and will be removed in a future release.

Specifies a list of notification keywords to be added the default set of keywords published to BES ("command_name=<command_name> ", "protocol_name=BEP"). Defaults to none.

Specifies whether to publish BES lifecycle events. (defaults to 'true').

Specifies the maximal size of stdout or stderr to be buffered in BEP, before it is reported as a progress event. Individual writes are still reported in a single event, even if larger than the specified value up to -- bes_outerr_chunk_size.

Specifies the maximal size of stdout or stderr to be sent to BEP in a single message.

Specifies the base URL where a user can view the information streamed to the BES backend. Bazel will output the URL appended by the invocation id to the terminal.

Specifies how long bazel should wait for the BES/BEP upload to complete after the build and tests have finished. A valid timeout is a natural number followed by a unit: Days (d), hours (h), minutes (m), seconds (s), and milliseconds (ms). The default value is '0' which means that there is no timeout.

Execute the build; this is the usual behaviour. Specifying --nobuild causes the build to stop before executing the build actions, returning zero iff the package loading and analysis phases completed successfully; this mode is useful for testing those phases.

If non-empty, write a varint delimited binary representation of representation of the build event protocol to that file.

Convert paths in the binary file representation of the build event protocol to more globally valid URIs whenever possible; if disabled, the file:// uri scheme will always be used

If non-empty, write a JSON serialisation of the build event protocol to that file.

The maximum number of entries for a single named_set_of_files event; values smaller than 2 are ignored and no event splitting is performed. This is intended for limiting the maximum event size in the build event protocol, although it does not directly control event size. The total event size is a function of the structure of the set as well as the file and uri lengths, which may in turn depend on the hash function.

Whether all actions should be published.

If non-empty, write a textual representation of the build event protocol to that file

Convert paths in the text file representation of the build event protocol to more globally valid URIs whenever possible; if disabled, the file:// uri scheme will always be used

Forces test targets tagged 'manual' to be built. 'manual' tests are excluded from processing. This option forces them to be built (but not executed).

Build python executable zip; on on Windows, off on other platforms

If true, build runfiles symlink forests for all targets. If false, write only manifests when possible.

If true, write runfiles manifests for all targets. If false, omit them.

Specifies a comma-separated list of tags. Each tag can be optionally preceded with '-' to specify excluded tags. Only those targets will be built that contain at least one included tag and do not contain any excluded tags. This option does not affect the set of tests executed with the 'test' command; those are be governed by the test filtering options, for example '--test_tag_filters'

If enabled, when building C++ tests statically and with fission the .dwp file for the test binary will be automatically built as well.

If specified, only *_test and test_suite rules will be built and other targets specified on the command line will be ignored. By default everything that was requested will be built.

If set to 'auto', Bazel reruns a test if and only if: (1) Bazel detects changes in the test or its dependencies, (2) the test is marked as external, (3) multiple test runs were requested with --runs_per_test, or(4) the test previously failed. If set to 'yes', Bazel caches all test results except for tests marked as external. If set to 'no', Bazel does not cache any test results.

Specifies a suffix to be added to the configuration directory.

Sets the prefixes of header files that a cc_proto_library creates.

Sets the prefixes of source files that a cc_proto_library creates.

Check the listed constraint.

Check that licensing constraints imposed by dependent packages do not conflict with distribution modes of the targets being built. By default, licenses are not checked.

Don't run tests, just check if they are up-to-date. If all tests results are up-to-date, the testing completes successfully. If any test needs to be built or executed, an error is reported and the testing fails. This option implies --check_up_to_date behavior. Using this option will also add: --check_up_to_date

If true, all rules and files under //third_party must declare licenses([])

Don't perform the build, just check if it is up-to-date. If all targets are up-to-date, the build completes successfully. If any step needs to be executed an error is reported and the build fails.

If disabled, visibility errors are demoted to warnings.

If specified, Bazel will instrument code (using offline instrumentation where possible) and will collect coverage information during tests. Only targets that match --instrumentation_filter will be affected. Usually this option should not be specified directly - 'bazel coverage' command should be used instead.

Use terminal controls to colorize output going to stderr.

Specifies desired cumulative coverage report type. At this point only HTML and LCOV reports are supported.

Specify the mode the binary will be built in. Values: 'fastbuild', 'dbg', 'opt'.

Compile a single dependency of the argument files. This is useful for syntax checking source files in IDEs, for example, by rebuilding a single target that depends on the source file to detect errors as early as possible in the edit/build/test cycle. This argument affects the way all non-flag arguments are interpreted; instead of being targets to build they are source filenames. For each source filename an arbitrary target that depends on it will be built.

The C++ compiler to use for compiling the target.

Selects additional config sections from the rc files; for every <command>, it also pulls in the options from <command>:<config> if such a section exists; if this section doesn't exist in any .rc file, Blaze fails with an error. The config sections and flag combinations they are equivalent to are located in the tools/*.blazerc config files.

Additional option to pass to gcc when compiling C source files.

Additional options to pass to gcc.

Location of the binary that is used to generate coverage reports. This must currently be a filegroup that contains a single file, the binary. Defaults to '//tools/test:coverage_report_generator'.

Location of support files that are required on the inputs of every test action that collects code coverage. Defaults to '//tools/test: coverage_support'.

The target CPU.

The label of the crosstool package to be used for compiling C++ code.

Use terminal cursor controls to minimize scrolling output going to stderr.

Specifies a custom malloc implementation. This setting overrides malloc attributes in build rules.

Additional option to pass to gcc when compiling C++ source files.

Whether to wait for the debugger before starting the app. Expands to: --start=DEBUG

Each --define option specifies an assignment for a build variable.

A comma-separated list of names of packages which the build system will consider non-existent, even if they are visible somewhere on the package path.Use this option when deleting a subpackage 'x/y' of an existing package 'x'. For example, after deleting x/y/BUILD in your client, the build system may complain if it encounters a label '//x:y/z' if that is still provided by another package_path entry. Specifying --deleted_packages x/y avoids this problem.

Whether to desugar Java 8 bytecode before dexing.

The adb device serial number. If not specified, the first device will be used.

If set, and compilation mode is not 'opt', objc apps will include debug entitlements when signing.

Discard the analysis cache immediately after the analysis phase completes. Reduces memory usage by ~10%, but makes further incremental builds slower.

A path to a directory where Bazel can read and write actions and action outputs. If the directory does not exist, it will be created.

Additional places to search for archives before accessing the network to download them.

Build all the tools used during the build for a distinct configuration from that used for the target program. When this is disabled, the same configuration is used for host and target programs. This may cause undesirable rebuilds of tools such as the protocol compiler (and then everything downstream) whenever a minor change is made to the target configuration, such as setting the linker options. When this is enabled (the default), a distinct configuration will be used to build the tools, preventing undesired rebuilds. However, certain libraries will then need to be compiled twice, once for each configuration, which may cause some builds to be slower. As a rule of thumb, this option is likely to benefit users that make frequent changes in configuration (e.g. opt/dbg). Please read the user manual for the full explanation.

Determines whether C++ binaries will be linked dynamically. 'default' means Bazel will choose whether to link dynamically. 'fully' means all libraries will be linked dynamically. 'off' means that all libraries will be linked in mostly static mode.

Embed source control revision or release label in binary

If set, apple_binary will generate and link objc protos into the output binary.

If set, use of fdo_absolute_profile_path will raise an error.

Enable runfiles symlink tree; By default, it's off on Windows, on on other platforms.

Enable toolchain resolution for the given toolchain type, if the rules used support that. This does not directly change the core Blaze machinery, but is a signal to participating rule implementations that toolchain resolution should be used.

Checks the environments each target is compatible with and reports errors if any target has dependencies that don't support the same environments

Expand test_suite targets into their constituent tests before analysis. When this flag is turned on (the default), negative target patterns will apply to the tests belonging to the test suite, otherwise they will not. Turning off this flag is useful when top-level aspects are applied at command line: then they can analyze test_suite targets.

Use action_listener to attach an extra_action to existing build actions.

Flag to help transition from allowing to disallowing srcs-less android_library rules with deps. The depot needs to be cleaned up to roll this out by default.

Compress Java resources in APKs

Use android databinding v2

Enables resource shrinking for android_binary APKs that use ProGuard.

use rex tool to rewrite dex files

If passed, resource merge conflicts will be treated as errors instead of warnings

Use dex2oat in parallel to possibly speed up android_test.

Convert paths in the json file representation of the build event protocol to more globally valid URIs whenever possible; if disabled, the file:// uri scheme will always be used

Selects how to upload artifacts referenced in the build event protocol.

Whether to double-check correct desugaring at Android binary level.

Whether to include supported Java 8 libraries in apps for legacy devices.

Specify a Docker image name (e.g. "ubuntu:latest") that should be used to execute a sandboxed action when using the docker strategy and the action itself doesn't already have a container-image attribute in its remote_execution_properties in the platform description. The value of this flag is passed verbatim to 'docker run', so it supports the same syntax and mechanisms as Docker itself.

If enabled, Bazel will pass the --privileged flag to 'docker run' when running actions. This might be required by your build, but it might also result in reduced hermeticity.

If enabled, injects the uid and gid of the current user into the Docker image before using it. This is required if your build / tests depend on the user having a name and home directory inside the container. This is on by default, but you can disable it in case the automatic image customization feature doesn't work in your case or you know that you don't need it.

If enabled, Bazel will print more verbose messages about the Docker sandbox strategy.

If set to true, enables the APIs required to support the Android Starlark migration.

Enable Docker-based sandboxing. This option has no effect if Docker is not installed.

Allows objc_* rules to depend on cc_library and causes any objc dependencies to be built with --cpu set to "ios_<--ios_cpu>" for any values in --ios_multi_cpu.

Log the executed spawns into this file as delimited Spawn protos.

Use external repositories for improved stability and speed when available.

Filters set of targets to schedule extra_actions for.

Only schedules extra_actions for top level targets.

If enabled, Bazel profiles the build and writes a JSON-format profile into a file in the output base.

Turn this off to disable checking the ctime of input files of an action before uploading it to a remote cache. There may be cases where the Linux kernel delays writing of files, which could cause false positives.

When enabled, check whether the dependencies of an aar_import are complete. This enforcement can break the build, or can just result in warnings.

If enabled, C++ .d files will be passed through in memory directly from the remote build nodes instead of being written to disk.

If enabled, the dependency (.jdeps) files generated from Java compilations will be passed through in memory directly from the remote build nodes instead of being written to disk.

No-op.

Whether to generate J2ObjC header map in parallel of J2ObjC transpilation.

Enables reduced classpaths for Java compilations.

If true, add --allowed_public_imports to the java compile actions.

If enabled, Bazel compresses the JSON-format profile with gzip.

This flag is experimental and may go away at any time. If true, dynamically linked binary targets will build and link their own srcs as a dynamic library instead of directly linking it in.

How many milliseconds should local execution be delayed, if remote execution was faster during a build at least once?

Estimate the actual memory available online. By default, Blaze assumes most actions use a fixed amount of memory, and counts that against the total available system memory, regardless of how much memory is actually available. This option enables online estimation of how much memory is available at any given time, and thus does not require accurate estimation of how much memory a given action will take.

This flag allows specifying multiple target CPUs. If this is specified, the --cpu option is ignored.

Whether to always compute MD5 digests of files with multiple threads. Might improve performance when using an SSD.

Enables module map generation and interpretation.

Uses these strings as objc fastbuild compiler options.

If set then ObjcCompile actions will have their action inputs reduced by running a tool to detect which headers are actually required for compilation.

If true, use libunwind for stack unwinding, and compile with -fomit-frame- pointer and -fasynchronous-unwind-tables.

If this flag is set to a value less than 100, Bazel will OOM if, after two full GC's, more than this percentage of the (old gen) heap is still occupied.

Enable the experimental persistent Java compiler. Expands to: --strategy=Javac=worker --strategy=JavaIjar=local -- strategy=JavaDeployJar=local --strategy=JavaSourceJar=local -- strategy=Turbine=local

If set to true, enables a number of platform-related Starlark APIs useful for debugging.

If set, Bazel will post the ProfilerStartedEvent including the path to the profile.

If set, Bazel will measure cpu usage and add it to the JSON profile.

Run extra actions for alternative Java api versions in a proto_library.

If specified, a path to a file to log gRPC call related details. This log consists of a sequence of serialized com.google.devtools.build.lib.remote.logging.RemoteExecutionLog.LogEntry protobufs with each message prefixed by a varint denoting the size of the following serialized protobuf message, as performed by the method LogEntry.writeDelimitedTo(OutputStream).

Whether to retry transient remote execution/cache errors.

The random factor to apply to retry delays on transient errors.

The maximum number of attempts to retry a transient error.

The maximum delay before retrying a transient error.

The multiplier by which to increase the retry delay on transient errors.

The initial delay before retrying a transient error.

Whether to use the experimental spawn cache infrastructure for remote caching. Enabling this flag makes Bazel ignore any setting for remote_executor.

If set, the repository cache will hardlink the file in case of a cache hit, rather than copying. This is inteded to save disk space.

If non-empty, specifies a file containing a resolved value, against which the repository directory hashes should be verified

If non-empty, write a Skylark value with the resolved information of all Starlark repository rules that were executed.

If non-empty read the specified resolved file instead of the WORKSPACE file

Lets the sandbox create its sandbox directories underneath this path. Specify a path on tmpfs (like /run/shm) to possibly improve performance a lot when your build / tests have many input files. Note: You need enough RAM and free space on the tmpfs to hold output and intermediate files generated by running actions.

Allow network access by default for actions.

Path to the sandboxfs binary to use when --experimental_use_sandboxfs is true. If a bare name, use the first binary of that name found in the PATH.

Scale all timeouts in Starlark repository rules by this factor. In this way, external repositories can be made working on machines that are slower than the rule author expected, without changing the source code

Enable dynamic execution by running actions locally and remotely in parallel. Bazel spawns each action locally and remotely and picks the one that completes first. If an action supports workers, the local action will be run in the persistent worker mode. To enable dynamic execution for an individual action mnemonic, use the `--internal_spawn_scheduler` and `--strategy=<mnemonic>=dynamic` flags instead. Expands to: --internal_spawn_scheduler --spawn_strategy=dynamic

If this flag is set, and a test action does not generate a test.xml file, then Bazel uses a separate action to generate a dummy test.xml file containing the test log. Otherwise, Bazel generates a test.xml as part of the test action.

If set to true, enables creation of configuration transition objects (the `transition()` function) in Starlark.

If this option is enabled, filesets will treat all output artifacts as regular files. They will not traverse directories or be sensitive to symlinks.

If true, checks that a Java target explicitly declares all directly used targets as dependencies.

Switches to an alternative progress bar that more explicitly shows progress, such as loaded packages and executed actions.

Number of concurrent actions shown in the alternative progress bar; each action is shown on a separate line. The alternative progress bar always shows at least one one, all numbers less than 1 are mapped to 1. This option has no effect unless --experimental_ui is set.

Make the experimental UI deduplicate messages to have a cleaner scroll-back log.

Number of bytes to which the experimental UI will limit its output (non-positive values indicate unlimited). Once the limit is approaching, the experimental UI will try hard to limit in a meaningful way, but will ultimately just drop all output.

If specified, Bazel will generate llvm-cov coverage map information rather than gcov when collect_code_coverage is enabled.

Use sandboxfs to create the actions' execroot directories instead of building a symlink tree.

If list of repository rules for which the hash of the output directory should be verified, provided a file is specified by -- experimental_repository_hash_file.

On Windows: if true, uses the C++ test wrapper to run tests, otherwise uses tools/test/test-setup.sh as on other platforms. On other platforms: no-op.

Log certain Workspace Rules events into this file as delimited WorkspaceEvent protos.

Causes the build system to explain each executed step of the build. The explanation is written to the specified log file.

Explicitly specify a dependency to JUnit or Hamcrest in a java_test instead of accidentally obtaining from the TestRunner's deps. Only works for bazel right now.

Location of a .entitlements file that is merged into any iOS signing action in this build.

The platforms that are available as execution platforms to run actions. Platforms can be specified by exact target, or as a target pattern. These platforms will be considered before those declared in the WORKSPACE file by register_execution_platforms().

The toolchain rules to be considered during toolchain resolution. Toolchains can be specified by exact target, or as a target pattern. These toolchains will be considered before those declared in the WORKSPACE file by register_toolchains().

Setting this option enables fat APKs, which contain native binaries for all specified target architectures, e.g., --fat_apk_cpu=x86,armeabi-v7a. If this flag is specified, then --android_cpu is ignored for dependencies of android_binary rules.

Generate binaries with FDO instrumentation. With Clang/LLVM compiler, it also accepts the directory name under which the raw profile file(s) will be dumped at runtime. Using this option will also add: --copt=-Wno-error

Use FDO profile information to optimize compilation. Specify the name of the zip file containing the .gcda file tree, or an afdo file containing an auto profile. This flag also accepts files specified as labels, for example //foo/bar:file.afdo. Such labels must refer to input files; you may need to add an exports_files directive to the corresponding package to make the file visible to Bazel. It also accepts a raw or an indexed LLVM profile file. This flag will be superseded by fdo_profile rule.

Use cache prefetch hints.

The fdo_profile representing the profile to be used for optimization.

The given features will be enabled or disabled by default for all packages. Specifying -<feature> will disable the feature globally. Negative features always override positive ones. This flag is used to enable rolling out default feature changes without a Bazel release.

Specifies which compilation modes use fission for C++ compilations and links. May be any combination of {'fastbuild', 'dbg', 'opt'} or the special values 'yes' to enable all modes and 'no' to disable all modes.

Each test will be retried up to the specified number of times in case of any test failure. Tests that required more than one attempt to pass would be marked as 'FLAKY' in the test summary. If this option is set, it should specify an int N or the string 'default'. If it's an int, then all tests will be run up to N times. If it is not specified or its value is 'default', then only a single test attempt will be made for regular tests and three for tests marked explicitly as flaky by their rule (flaky=1 attribute).

Forces --experimental_external_repositories.

If enabled, all C++ compilations produce position-independent code ("- fPIC"), links prefer PIC pre-built libraries over non-PIC libraries, and links produce position-independent executables ("-pie").

Deprecated alias for `--python_version`. Disabled by `-- incompatible_remove_old_python_version_api`.

Specify how to execute genrules. This flag will be phased out. Instead, use --spawn_strategy=<value> to control all actions or --strategy=Genrule=<value> to control genrules only.

A comma-separated list of Google Cloud authentication scopes.

Specifies the file to get authentication credentials from. See https://cloud.google.com/docs/authentication for details.

Whether to use 'Google Application Default Credentials' for authentication. See https://cloud.google.com/docs/authentication for details. Disabled by default.

A label to a checked-in libc library. The default value is selected by the crosstool toolchain, and you almost never need to override it.

Mnemonics of workers to run with high priority. When high priority workers are running all other workers are throttled.

Specify the mode the tools used during the build will be built in. Values: 'fastbuild', 'dbg', 'opt'.

The C++ compiler to use for host compilation. It is ignored if -- host_crosstool_top is not set.

Additional option to pass to gcc when compiling C source files for host tools.

Additional options to pass to gcc for host tools.

The host CPU.

By default, the --crosstool_top and --compiler options are also used for the host configuration. If this flag is provided, Bazel uses the default libc and compiler for the given crosstool_top.

Additional options to pass to gcc for host tools.

Overrides the Python version for the host configuration. Can be "PY2" or "PY3".

If specified, this setting overrides the libc top-level directory (-- grte_top) for the host configuration.

The Java launcher used by tools that are executed during a build.

The Java toolchain used to build tools that are executed during a build.

JAVABASE used for the host JDK. This is the java_runtime which is used to execute tools during a build.

Additional options to pass to javac when building tools that are executed during a build.

Additional option to pass to gcc when linking host tools.

The label of a platform rule that describes the host system.

Additional options to pass to swiftc for host tools.

Do not print a warning when sandboxed execution is not supported on this system.

If true, Python rules use the new PY2/PY3 version semantics. For more information, see the documentation for `py_binary`'s `python_version` attribute.

If set to true, all `load` must be called at the top of .bzl files, before any other statement.

If specified, Bazel will use gcov to collect code coverage for C++ test targets. This option only works for gcc compilation.

If set to true, depset type is not iterable. For loops and functions expecting an iterable will reject depset objects. Use the `.to_list` method to explicitly convert to a list.

If set to true, depset union using `+`, `|` or `.union` are forbidden. Use the `depset` constructor instead.

If true, Bazel will not allow using the CROSSTOOL file for cc toolchain configuration. Instead, cc_toolchain should have a toolchain_config attribute that points to a rule written in Starlark that provides a CcToolchainConfigInfo provider. See https://github. com/bazelbuild/bazel/issues/7320 for more info.

If set to true, disable the deprecated parameters 'single_file' and 'non_empty' on attribute definition methods, such as attr.label().

If true, Bazel will not allow specifying expand_if_all_available in flag_sets(see https://github.com/bazelbuild/bazel/issues/7008 for migration instructions).

If true, Bazel will not read crosstool flags from legacy crosstool fields (see https://github.com/bazelbuild/bazel/issues/6861 for migration instructions).

If set to true, disallow use of deprecated resource fields on the Objc provider.

Deprecated no-op.

If true, disables all license checking logic. This overrides -- check_third_party_targets_have_licenses

If set to true, rule attributes cannot set 'cfg = "data"', which is a noop.

If set to true, the `+` becomes disabled for dicts.

If set to true, function `FileType` is not available.

If set to true, usages of old .java provider are disallowed.

If set to true, old-style JavaInfo provider construction is disallowed.

If set to true, native Python rules will neither produce nor consume the legacy "py" provider. Use PyInfo instead. Under this flag, passing the legacy provider to a Python target will be an error.

If set to true, the label argument to 'load' cannot cross a package boundary.

If set to true, the native module is not accessible in BUILD files. Use for example `cc_library` instead of `native.cc_library`.

If set to true, vectorized calls to Args#add are disallowed.

If set to true, rule implementation functions may not return a struct. They must instead return a list of provider instances.

Deprecated no-op.

If true, Bazel will not enable 'host' and 'nonhost' features in the c++ toolchain (see https://github.com/bazelbuild/bazel/issues/7407 for more information).

Controls whether directories are expanded to the list of files under that directory when added to Args, instead of replaced by the path of the directory.

If true Bazel will use a new way of computing code coverage for java targets. It allows collecting coverage for Starlark JVM rules and java_import. Only includes JVM files in the coverage report (e.g. dismisses data files). The report includes the actual path of the files relative to the workspace root instead of the package path (e.g. src/com/google/Action. java instead of com/google/Action.java.

Deprecated no-op.

See https://github.com/bazelbuild/bazel/issues/7480

If true, the genfiles directory is folded into the bin directory.

If set to true, the API to create actions is only available on `ctx. actions`, not on `ctx`.

If set to true, disables the function `attr.license`.

If set to true, disables the `default` parameter of the `attr.output` and `attr.output_list` attribute definition functions.

If set to true, tools should be passed to `ctx.actions.run()` and `ctx. actions.run_shell()` using the `tools` parameter instead of the `inputs` parameter. Furthermore, if this flag is set and a `tools` parameter is not passed to the action, it is an error for any tools to appear in the `inputs`.

If set to true, disables the output_group field of the 'Target' Starlark type.

If set to true, only symbols explicitly defined in the file can be loaded; symbols introduced by load are not implicitly re-exported.

If true, targets built in the Python 2 configuration will appear under an output root that includes the suffix '-py2', while targets built for Python 3 will appear in a root with no Python-related suffix. This means that the `bazel-bin` convenience symlink will point to Python 3 targets rather than Python 2. If you enable this option it is also recommended to enable `-- incompatible_py3_is_default`.

If true, `py_binary` and `py_test` targets that do not set their `python_version` (or `default_python_version`) attribute will default to PY3 rather than to PY2. It is an error to set this flag without also enabling `--incompatible_allow_python_version_transitions`. If you set this flag it is also recommended to set `-- incompatible_py2_outputs_are_suffixed`.

If set to true, will treat references to '@<main repo name>' the same as '@'.

If set to true, Bazel will represent symlinks in action outputs in the remote caching/execution protocol as such. The current behavior is for remote caches/executors to follow symlinks and represent them as files. See #6631 for details.

If true, Bazel will complain when cc_toolchain.cpu and cc_toolchain. compiler attribtues are set (see https://github. com/bazelbuild/bazel/issues/7075 for migration instructions).

If true, Bazel will not link library dependencies as whole archive by default (see https://github.com/bazelbuild/bazel/issues/7362 for migration instructions).

If set to true, the native maven_jar rule is disabled; only the Starlark version will be available

If true, disables use of the `--force_python` flag and the `default_python_version` attribute for `py_binary` and `py_test`. Use the `--python_version` flag and `python_version` attribute instead, which have exactly the same meaning. This flag also disables `select()`-ing over `-- host_force_python`.

If true, cc_toolchain_info.use_pic_for_dynamic_libraries will require feature_configuration argument (see #7007).

If true, Bazel uses an environment with a static value for PATH and does not inherit LD_LIBRARY_PATH or TMPDIR. 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.

If set to true, the order of arguments is stricter in function calls, see https://github.com/bazelbuild/bazel/issues/6611

Propagates Objective-C module maps only to direct dependencies in the 'objc' provider, not to all transitive dependencies.

If enabled, the sandbox will expand tree artifacts in runfiles, thus the files that are contained in the tree artifact will be symlinked as individual files.

Switch the Android rules to use aapt2 by default for resource processing. To resolve issues when migrating your app to build with aapt2, see https: //developer.android.com/studio/command-line/aapt2#aapt2_changes

If enabled, uses the remote Java tools for the default -- host_java_toolchain. See #7197.

If enabled, uses the remote Java tools for the default --java_toolchain. See #7196.

If set to true, java_common APIs that take a java_toolchain or host_javabase parameter require a JavaTootoolchainInfo or JavaRuntimeInfo instead of a configured target.

On Linux/macOS/non-Windows: no-op. On Windows: this flag affects how java_binary and java_test targets are built; in particular, how the launcher of these targets escapes flags at the time of running the java_binary/java_test. When the flag is true, the launcher escapes the JVM flags using Windows-style escaping (correct behavior). When the flag is false, the launcher uses Bash-style escaping (buggy behavior). See https: //github.com/bazelbuild/bazel/issues/7072

Whether to do an incremental install. If true, try to avoid unnecessary additional work by reading the state of the device the code is to be installed on and using that information to avoid unnecessary work. If false (the default), always do a full install.

Does most of the work for dexing separately for each Jar file.

The verbosity for incremental install. Set to 1 for debug logging.

When coverage is enabled, specifies whether to consider instrumenting test rules. When set, test rules included by --instrumentation_filter are instrumented. Otherwise, test rules are always excluded from coverage instrumentation.

When coverage is enabled, only rules with names included by the specified regex-based filter will be instrumented. Rules prefixed with '-' are excluded instead. Note that only non-test rules are instrumented unless -- instrument_test_targets is enabled.

Use interface shared objects if supported by the toolchain. All ELF toolchains currently support this setting.

Specifies to target CPU of iOS compilation.

Enable checking for memory leaks in ios_test targets.

Minimum compatible iOS version for target simulators and devices.

Comma-separated list of architectures to build an ios_application with. The result is a universal binary containing all specified architectures.

Specifies the version of the iOS SDK to use to build iOS applications.

Certificate name to use for iOS signing. If not set will fall back to provisioning profile. May be the certificate's keychain identity preference or (substring) of the certificate's common name, as per codesign's man page (SIGNING IDENTITIES).

The device to simulate when running an iOS application in the simulator, e. g. 'iPhone 6'. You can get a list of devices by running 'xcrun simctl list devicetypes' on the machine the simulator will be run on.

The version of iOS to run on the simulator when running or testing. This is ignored for ios_test rules if a target device is specified in the rule.

Additional options to pass to the J2ObjC tool.

Causes the Java virtual machine of a java test to wait for a connection from a JDWP-compliant debugger (such as jdb) before starting the test. Implies -test_output=streamed. Expands to: --test_arg=--wrapper_script_flag=--debug -- test_output=streamed --test_strategy=exclusive --test_timeout=9999 -- nocache_test_results

Generate dependency information (for now, compile-time classpath) per Java target.

Compile ijars directly from source.

The Java launcher to use when building Java binaries. The "launcher" attribute overrides this flag.

The name of the toolchain rule for Java.

JAVABASE used for the JDK invoked by Blaze. This is the java_runtime which will be used to execute external Java commands.

Additional options to pass to javac.

The number of concurrent jobs to run. Takes {@value FLAG_SYNTAX}. Values must be between 1 and5000 values above 2500 may cause memory issues. "auto" calculates a reasonable default based on host resources.

Additional options to pass to the Java VM. These options will get added to the VM startup options of each java_binary target.

Continue as much as possible after an error. While the target that failed and those that depend on it cannot be analyzed, other prerequisites of these targets can be.

If false, Blaze will discard the inmemory state from this build when the build finishes. Subsequent builds will not have any incrementality with respect to this one.

If true, build runfiles symlink forests for external repositories under . runfiles/wsname/external/repo (in addition to .runfiles/repo).

Use this to suppress generation of the legacy important_outputs field in the TargetComplete event.

Deprecated, superseded by --incompatible_remove_legacy_whole_archive (see https://github.com/bazelbuild/bazel/issues/7362 for details). When on, use --whole-archive for cc_binary rules that have linkshared=1 and either linkstatic=1 or '-static' in linkopts. This is for backwards compatibility only. A better alternative is to use alwayslink=1 where required.

Additional option to pass to gcc when linking.

Number of parallel threads to use for the loading/analysis phase.Takes an integer, or a keyword ("auto", "HOST_CPUS", "HOST_RAM"), optionally followed by an operation ([-|*]<float>) eg. "auto", "HOST_CPUS*.5". "auto" sets a reasonable default based onhost resources. Must be at least 1.

Explicitly set the number of local CPU threads available to Bazel. Takes an integer, or "HOST_CPUS", optionally followed by [-|*]<float> (eg. HOST_CPUS*.5 to use half the available CPU cores).By default, ("HOST_CPUS"), Bazel will query system configuration to estimate number of CPU cores available for the locally executed build actions. Note: This is a no-op if --local_resources is set.

Explicitly set the amount of local host RAM (in MB) available to Bazel. Takes an integer, or "HOST_RAM", optionally followed by [-|*]<float> (eg. HOST_RAM*.5 to use half the available RAM).By default, ("HOST_RAM*.67"), Bazel will query system configuration to estimate amount of RAM available for the locally executed build actions and will use 67% of available RAM. Note: This is a no-op if --ram_utilization_factor or --local_resources is set.

Explicitly set amount of local resources available to Blaze. By default, Bazel will query system configuration to estimate amount of RAM (in MB) and number of CPU cores available for the locally executed build actions. It would also assume default I/O capabilities of the local workstation (1.0). This options allows to explicitly set all 3 values. Note, that if this option is used, Bazel will ignore --ram_utilization_factor, --local_cpu_resources, and --local_ram_resources.

Time to wait between terminating a local process due to timeout and forcefully shutting it down.

The max number of local test jobs to run concurrently. Takes an integer, or a keyword ("auto", "HOST_CPUS", "HOST_RAM"), optionally followed by an operation ([-|*]<float>) eg. "auto", "HOST_CPUS*.5". 0 means local resources will limit the number of local test jobs to run concurrently instead. Setting this greater than the value for --jobs is ineffectual.

The logging level.

Additional option to pass to the LTO backend step (under -- features=thin_lto).

Additional option to pass to the LTO indexing step (under -- features=thin_lto).

Comma-separated list of architectures for which to build Apple macOS binaries.

Minimum compatible macOS version for targets.

Specifies the version of the macOS SDK to use to build macOS applications.

Writes intermediate parameter files to output tree even when using remote action execution. Useful when debugging actions.

When discarding the analysis cache due to a change in the build options, displays up to the given number of changed option names. If the number given is -1, all changed options will be displayed.

Tune memory profile's computation of stable heap at end of build. Should be two integers separated by a comma. First parameter is the number of GCs to perform. Second parameter is the number of seconds to wait between GCs.

The message translations used for translating messages in Java targets.

The minimum OS version which your compilation targets.

Select how to run mobile-install. "classic" runs the current version of mobile-install. "skylark" uses the new skylark version, which has support for android_test.

Add or remove keys from an action's execution info based on action mnemonic. Applies only to actions which support execution info. Many common actions support execution info, e.g. Genrule, CppCompile, Javac, SkylarkAction, TestRunner. When specifying multiple values, order matters because many regexes may apply to the same mnemonic. Syntax: "regex=[+-]key,[+-]key,...". Examples: '.*=+x,.*=-y,.*=+z' adds 'x' and 'z' to, and removes 'y' from, the execution info for all actions. 'Genrule=+requires-x' adds 'requires-x' to the execution info for all Genrule actions. '(?!Genrule).*=-requires-x' removes 'requires-x' from the execution info for all non-Genrule actions.

If set, and compilation mode is set to 'dbg', define GLIBCXX_DEBUG, GLIBCXX_DEBUG_PEDANTIC and GLIBCPP_CONCEPT_CHECKS.

Whether to perform symbol and dead-code strippings on linked binaries. Binary strippings will be performed if both this flag and -- compilationMode=opt are specified.

Specifies whether to generate a linkmap file.

Location of tool to scan Objective-C code for inclusions and output a . headers_list file.

The maximum number of source files to process within in each header scanning action.

If set, .d files emitted by clang will be used to prune the set of inputs passed into objc compiles.

Additional options to pass to Objective C compilation.

Only shows warnings for rules with a name matching the provided regular expression.

Specifies which output groups of the top-level targets to build. If omitted, a default set of output groups are built. When specified the default set is overridden. However you may use -- output_groups=+<output_group> or --output_groups=-<output_group> to instead modify the set of output groups.

Overrides a repository with a local directory.

A colon-separated list of where to look for packages. Elements beginning with '%workspace%' are relative to the enclosing workspace. If omitted or empty, the default is the output of 'bazel info default-package-path'.

If enabled, the parse_headers feature verifies that a header module can be built for the target in question instead of doing a separate compile of the header.

Additional options to selectively pass to gcc when compiling certain files. This option can be passed multiple times. Syntax: regex_filter@option_1, option_2,...,option_n. Where regex_filter stands for a list of include and exclude regular expression patterns (Also see --instrumentation_filter). option_1 to option_n stand for arbitrary command line options. If an option contains a comma it has to be quoted with a backslash. Options can contain @. Only the first @ is used to split the string. Example: -- per_file_copt=//foo/.*\.cc,-//foo/bar\.cc@-O0 adds the -O0 command line option to the gcc command line of all cc files in //foo/ except bar.cc.

Additional options to selectively pass to LTO backend (under -- features=thin_lto) when compiling certain backend objects. This option can be passed multiple times. Syntax: regex_filter@option_1,option_2,..., option_n. Where regex_filter stands for a list of include and exclude regular expression patterns. option_1 to option_n stand for arbitrary command line options. If an option contains a comma it has to be quoted with a backslash. Options can contain @. Only the first @ is used to split the string. Example: --per_file_ltobackendopt=//foo/.*\.o,-//foo/bar\.o@-O0 adds the -O0 command line option to the LTO backend command line of all o files in //foo/ except bar.o.

Enable the persistent Android resource processor by using workers. Expands to: --internal_persistent_busybox_tools -- strategy=AaptPackage=worker --strategy=AndroidResourceParser=worker -- strategy=AndroidResourceValidator=worker -- strategy=AndroidResourceCompiler=worker --strategy=RClassGenerator=worker --strategy=AndroidResourceLink=worker --strategy=AndroidAapt2=worker -- strategy=AndroidAssetMerger=worker -- strategy=AndroidResourceMerger=worker -- strategy=AndroidCompiledResourceMerger=worker

Specifies a suffix to be added to the configuration directory.

The labels of the platform rules describing the target platforms for the current command.

Plugins to use in the build. Currently works with java_plugin.

When building a target //a:a, process headers in all targets that //a:a depends on (if header processing is enabled for the toolchain).

If set, profile Bazel and write data to the specified file. Use bazel analyze-profile to analyze the profile.

Show the command progress in the terminal title. Useful to see what bazel is doing when having multiple terminal tabs.

The number of seconds to wait between two reports on still running jobs. The default value 0 means to use the default 10:30:60 incremental algorithm.

Specifies which version of ProGuard to use for code removal when building a Java binary.

Specifies the BES project identifier. Defaults to null.

The label of the proto-compiler.

Label of proto_lang_toolchain() which describes how to compile C++ protos

Label of proto_lang_toolchain() which describes how to compile j2objc protos

Label of proto_lang_toolchain() which describes how to compile Java protos

Label of proto_lang_toolchain() which describes how to compile JavaLite protos

Additional options to pass to the protobuf compiler.

The absolute path of the Python interpreter invoked by Bazel.

The label of py_runtime rule used for the Python interpreter invoked by Bazel.

The Python major version mode, either `PY2` or `PY3`. Note that under the new version semantics (`--incompatible_allow_python_version_transitions`) this is overridden by `py_binary` and `py_test` targets (even if they don't explicitly specify a version) so there is usually not much reason to supply this flag.

Local path to the Python2 executable. Deprecated, please use python_path or python_top instead.

Local path to the Python3 executable. Deprecated, please use python_path or python_top instead.

Specify what percentage of the system's RAM Bazel should try to use for its subprocesses. This option affects how many processes Bazel will try to run in parallel. If you run several Bazel builds in parallel, using a lower value for this option may avoid thrashing and thus improve overall throughput. Using a value higher than 67 is NOT recommended. Note that Blaze's estimates are very coarse, so the actual RAM usage may be much higher or much lower than specified. Note also that this option does not affect the amount of memory that the Bazel server itself will use. Setting this value overrides --local_ram_resources

Whether to accept remotely cached action results.

If true, upload action symlink outputs to the remote cache. If this option is not enabled, cachable actions that output symlinks will fail.

HOST or HOST:PORT of a remote caching endpoint.

Connect to the remote cache through a proxy. Currently this flag can only be used to configure a Unix domain socket (unix:/path/to/socket) for the HTTP cache.

Set the default platform properties to be set for the remote execution API, if the execution platform does not already set remote_execution_properties. This value will also be used if the host platform is selected as the execution platform for remote execution.

The relative priority of actions to be executed remotely. The semantics of the particular priority values are server-dependent.

HOST or HOST:PORT of a remote execution endpoint.

A base URL of a HTTP caching service. Both http:// and https:// are supported. BLOBs are stored with PUT and retrieved with GET. See remote/README.md for more information.

Value to pass as instance_name in the remote execution API.

Whether to fall back to standalone local execution strategy if remote execution fails.

The strategy to use when remote execution has to fallback to local execution.

The max. number of concurrent network connections to the remote cache/executor. By default Bazel limits the number of TCP connections to 100. Setting this flag to 0 will make Bazel choose the number of connections automatically.

The relative priority of remote actions to be stored in remote cache. The semantics of the particular priority values are server-dependent.

The maximum number of seconds to wait for remote execution and cache calls. For the REST cache, this is both the connect and the read timeout.

Whether to upload locally executed action results to the remote cache.

If set to true, Bazel will compute the hash sum of all remote downloads and discard the remotely cached values if they don't match the expected value.

Specifies the cache location of the downloaded values obtained during the fetching of external repositories. An empty string as argument requests the cache to be disabled.

This flag has no effect, and is deprecated

Prefix to insert in front of command before running. Examples: --run_under=valgrind --run_under=strace --run_under='strace -c' --run_under='valgrind --quiet --num-callers=20' --run_under=//package:target --run_under='//package:target --options'

Specifies number of times to run each test. If any of those attempts fail for any reason, the whole test would be considered failed. Normally the value specified is just an integer. Example: --runs_per_test=3 will run all tests 3 times. Alternate syntax: regex_filter@runs_per_test. Where runs_per_test stands for an integer value and regex_filter stands for a list of include and exclude regular expression patterns (Also see --instrumentation_filter). Example: --runs_per_test=//foo/.*,-//foo/bar/.*@3 runs all tests in //foo/ except those under foo/bar three times. This option can be passed multiple times.

If true, any shard in which at least one run/attempt passes and at least one run/attempt fails gets a FLAKY status.

Add additional path pair to mount in sandbox.

For sandboxed actions, disallow access to this path.

Enables debugging features for the sandboxing feature. This includes two things: first, the sandbox root contents are left untouched after a build (and if sandboxfs is in use, the file system is left mounted); and second, prints extra debugging information on execution. This can help developers of Bazel or Starlark rules with debugging failures due to missing input files, etc.

Change the current hostname to 'localhost' for sandboxed actions.

Change the current username to 'nobody' for sandboxed actions.

For sandboxed actions, mount an empty, writable directory at this path (if supported by the sandboxing implementation, ignored otherwise).

For sandboxed actions, make an existing directory writable in the sandbox (if supported by the sandboxing implementation, ignored otherwise).

If set, temporary outputs from gcc will be saved. These include .s files (assembler code), .i files (preprocessed C) and .ii files (preprocessed C++).

If true, native libraries that contain identical functionality will be shared among different targets

Absolute path to the shell executable for Bazel to use. If this is unset, but the BAZEL_SH environment variable is set on the first Bazel invocation (that starts up a Bazel server), Bazel uses that. If neither is set, Bazel uses a hard-coded default path depending on the operating system it runs on (Windows: c:/tools/msys64/usr/bin/bash.exe, FreeBSD: /usr/local/bin/bash, all others: /bin/bash). Note that using a shell that is not compatible with bash may lead to build failures or runtime failures of the generated binaries.

If enabled, causes Bazel to print "Loading package:" messages.

Display progress messages during a build.

Minimum number of seconds between progress messages in the output.

Show the results of the build. For each target, state whether or not it was brought up-to-date, and if so, a list of output files that were built. The printed files are convenient strings for copy+pasting to the shell, to execute them. This option requires an integer argument, which is the threshold number of targets above which result information is not printed. Thus zero causes suppression of the message and MAX_INT causes printing of the result to occur always. The default is one.

Display progress messages when tasks complete, not just when they start.

Include timestamps in messages

Specify how spawn actions are executed by default. 'standalone' means run all of them locally without any kind of sandboxing. 'sandboxed' means to run them in a sandboxed environment with limited privileges (details depend on platform support).

Whether to use split apks to install and update the application on the device. Works only with devices with Marshmallow or later

Stamp binaries with the date, username, hostname, workspace information, etc.

How the app should be started after installing it. Set to WARM to preserve and restore application state on incremental installs.

Whether to start the app after installing it. Expands to: --start=COLD

Specify how to distribute compilation of other spawn actions. Example: 'Javac=local' means to spawn Java compilation locally. 'JavaIjar=sandboxed' means to spawn Java Ijar actions in a sandbox.

Override which spawn strategy should be used to execute spawn actions that have descriptions matching a certain regex_filter. See --per_file_copt for details onregex_filter matching. The first regex_filter that matches the description is used. This option overrides other flags for specifying strategy. Example: --strategy_regexp=//foo.*\.cc,-//foo/bar=local means to run actions using local strategy if their descriptions match //foo.*.cc but not //foo/bar. Example: --strategy_regexp='Compiling.*/bar=local --strategy_regexp=Compiling=sandboxed will run 'Compiling //foo/bar/baz' with the 'local' strategy, but reversing the order would run it with 'sandboxed'.

If this option is enabled, filesets crossing package boundaries are reported as errors. It does not work when check_fileset_dependencies_recursively is disabled.

Unless OFF, checks that a proto_library target explicitly declares all directly used targets as dependencies.

If true, headers found through system include paths (-isystem) are also required to be declared.

Specifies whether to strip binaries and shared libraries (using "-Wl,-- strip-debug"). The default value of 'sometimes' means strip iff -- compilation_mode=fastbuild.

Additional options to pass to strip when generating a '<name>.stripped' binary.

Display the subcommands executed during a build.

Additional options to pass to Swift compilation.

The prefix that is prepended to any of the convenience symlinks that are created after a build. If '/' is passed, then no symlinks are created and no warning is emitted. If omitted, the default value is the name of the build tool.

Declares this build's target environment. Must be a label reference to an "environment" rule. If specified, all top-level targets must be compatible with this environment.

Specifies additional options and arguments that should be passed to the test executable. Can be used multiple times to specify several arguments. If multiple tests are executed, each of them will receive identical arguments. Used only by the 'bazel test' command.

Specifies additional environment variables to be injected into the test runner environment. Variables can be either specified by name, in which case its value will be read from the Bazel client environment, or by the name=value pair. This option can be used multiple times to specify several variables. Used only by the 'bazel test' command.

Specifies a filter to forward to the test framework. Used to limit the tests run. Note that this does not affect which targets are built.

When disabled, any non-passing test will cause the entire build to stop. By default all tests are run, even if some do not pass.

Specifies a comma-separated list of test languages. Each language can be optionally preceded with '-' to specify excluded languages. Only those test targets will be found that are written in the specified languages. The name used for each language should be the same as the language prefix in the *_test rule, e.g. one of 'cc', 'java', 'py', etc. This option affects --build_tests_only behavior and the test command.

Specifies desired output mode. Valid values are 'summary' to output only test status summary, 'errors' to also print test logs for failed tests, 'all' to print logs for all tests and 'streamed' to output logs for all tests in real time (this will force tests to be executed locally one at a time regardless of --test_strategy value).

This option is deprecated and has no effect.

Specify strategy for test sharding: 'explicit' to only use sharding if the 'shard_count' BUILD attribute is present. 'disabled' to never use test sharding.

Specifies a comma-separated list of test sizes. Each size can be optionally preceded with '-' to specify excluded sizes. Only those test targets will be found that contain at least one included size and do not contain any excluded sizes. This option affects --build_tests_only behavior and the test command.

Specifies which strategy to use when running tests.

Specifies the desired format ot the test summary. Valid values are 'short' to print information only about tests executed, 'terse', to print information only about unsuccessful tests that were run, 'detailed' to print detailed information about failed test cases, and 'none' to omit the summary.

Specifies a comma-separated list of test tags. Each tag can be optionally preceded with '-' to specify excluded tags. Only those test targets will be found that contain at least one included tag and do not contain any excluded tags. This option affects --build_tests_only behavior and the test command.

Override the default test timeout values for test timeouts (in secs). If a single positive integer value is specified it will override all categories. If 4 comma-separated integers are specified, they will override the timeouts for short, moderate, long and eternal (in that order). In either form, a value of -1 tells blaze to use its default timeouts for that category.

Specifies a comma-separated list of test timeouts. Each timeout can be optionally preceded with '-' to specify excluded timeouts. Only those test targets will be found that contain at least one included timeout and do not contain any excluded timeouts. This option affects --build_tests_only behavior and the test command.

Specifies the base temporary directory for 'bazel test' to use.

Specify the TLS client certificate to use.

Specifies whether to use TLS for remote execution/caching and the build event service (BES).

A tool name to attribute this Bazel invocation to.

Print debug information while finding toolchains for a rule. This might help developers of Bazel or Starlark rules with debugging failures due to missing toolchains.

If false, Blaze will not persist data that allows for invalidation and re- evaluation on incremental builds in order to save memory on this build. Subsequent builds will not have any incrementality with respect to this one. Usually you will want to specify --batch when setting this to false.

Translate Java messages; bundle all translations into the jar for each affected rule.

When enabled, test-related options will be cleared below the top level of the build. When this flag is active, tests cannot be built as dependencies of non-test rules, but changes to test-related options will not cause non- test rules to be re-analyzed.

Comma-separated list of architectures for which to build Apple tvOS binaries.

Minimum compatible tvOS version for target simulators and devices.

Specifies the version of the tvOS SDK to use to build tvOS applications.

The device to simulate when running an tvOS application in the simulator, e. g. 'Apple TV 1080p'. You can get a list of devices by running 'xcrun simctl list devicetypes' on the machine the simulator will be run on.

The version of tvOS to run on the simulator when running or testing.

If enabled, this option causes Java compilation to use interface jars. This will result in faster incremental compilation, but error messages can be different.

Build Android APKs with SingleJar.

Increases the verbosity of the explanations issued if --explain is enabled. Has no effect if --explain is not enabled.

If a command fails, print out the full command line.

If true, bazel tries to use the operating system's file watch service for local changes instead of scanning every file for a change.

Comma-separated list of architectures for which to build Apple watchOS binaries.

Minimum compatible watchOS version for target simulators and devices.

Specifies the version of the watchOS SDK to use to build watchOS applications.

The device to simulate when running an watchOS application in the simulator, e.g. 'Apple Watch - 38mm'. You can get a list of devices by running 'xcrun simctl list devicetypes' on the machine the simulator will be run on.

The version of watchOS to run on the simulator when running or testing.

Extra command-flags that will be passed to worker processes in addition to --persistent_worker, keyed by mnemonic (e.g. --worker_extra_flag=Javac=--debug.

How many instances of a worker process (like the persistent Java compiler) may be launched if you use the 'worker' strategy. May be specified as [name=value] to give a different value per worker mnemonic. Takesan integer, or a keyword ("auto", "HOST_CPUS", "HOST_RAM"), optionally followed by an operation ([-|*]<float>) eg. "auto", "HOST_CPUS*.5". 'auto' calculates a reasonable default based on machine capacity."=value" sets a default for unspecified mnemonics.

If enabled, all workers quit after a build is done.

If enabled, workers will be executed in a sandboxed environment.

If enabled, prints verbose messages when workers are started, shutdown, ...

A command invoked at the beginning of the build to provide status information about the workspace in the form of key/value pairs. See the User's Manual for the full specification.

Use XbinaryFDO profile information to optimize compilation. Specify the name of default cross binary profile. When the option is used together with --fdo_instrument/--fdo_optimize/--fdo_profile, those options will always prevail as if xbinary_fdo is never specified.

If specified, uses Xcode of the given version for relevant build actions. If unspecified, uses the executor default version of Xcode.

The label of the xcode_config rule to be used for selecting the Xcode version in the build configuration.