allbuildtestrunquerystartup options
--action_cache=<true or false>
Dump action cache content.
default: "false"
bazel monitoring
dump
--action_env=<'name=value' assignment with an optional value part>
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.
may be used multiple times
action command_lines
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--action_graph=<string>
Dump action graph to the specified path.
default: see description
bazel monitoring
dump
--action_graph:include_artifacts=<true or false>
Include inputs and outputs actions in the action graph dump. This option does only apply to --action_graph.
default: "true"
bazel monitoring
dump
--action_graph:include_cmdline=<true or false>
Include command line of actions in the action graph dump. This option does only apply to --action_graph.
default: "false"
bazel monitoring
dump
--action_graph:targets=<comma-separated list of options>
Comma separated list of targets to include in action graph dump. Defaults to all attributes. This option does only apply to --action_graph.
default: "..."
bazel monitoring
dump
--adb=<string>
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.
default: ""
changes inputs
mobile-install
--adb_arg=<string>
Extra arguments to pass to adb. Usually used to designate a device to install to.
may be used multiple times
action command_lines
mobile-install
--all_incompatible_changes
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_bzl_disallow_load_after_statement -- incompatible_depset_is_not_iterable --incompatible_depset_union -- incompatible_disable_deprecated_attr_params -- incompatible_disable_objc_provider_resources -- incompatible_disable_third_party_license_checking -- incompatible_disallow_dict_plus --incompatible_disallow_filetype -- incompatible_disallow_legacy_java_provider -- incompatible_disallow_legacy_javainfo -- incompatible_disallow_load_labels_to_cross_package_boundaries -- incompatible_disallow_native_in_build_file -- incompatible_disallow_old_style_args_add -- incompatible_disallow_struct_provider_syntax -- incompatible_do_not_split_linking_cmdline -- incompatible_expand_directories --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_remap_main_repo --incompatible_remove_native_maven_jar -- incompatible_string_join_requires_strings -- incompatible_use_toolchain_providers_in_java_common
--allow_analysis_failures=<true or false>
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.
default: "false"
loading and_analysis
experimental
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--analysis_testing_deps_limit=<integer>
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.
--android_aapt=<aapt, aapt2 or auto>
Selects the version of androidAaptVersion to use for android_binary rules. Flag to help the test and transition to aapt2.
default: "auto"
affects outputs
loading and_analysis
loses incremental_state
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--android_compiler=<string>
The Android target compiler.
default: see description
affects outputs
loading and_analysis
loses incremental_state
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--android_cpu=<string>
The Android target CPU.
default: "armeabi-v7a"
affects outputs
loading and_analysis
loses incremental_state
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--android_crosstool_top=<build target label>
The location of the C++ compiler used for Android builds.
default: "//external:android/crosstool"
affects outputs
changes inputs
loading and_analysis
loses incremental_state
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--android_databinding_use_v3_4_args=<true or false>
Use android databinding v2 with 3.4.0 argument
default: "false"
affects outputs
loading and_analysis
loses incremental_state
experimental
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--android_dynamic_mode=<off, default or fully>
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.
default: "off"
affects outputs
loading and_analysis
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--android_grte_top=<label>
The Android target grte_top.
default: see description
changes inputs
loading and_analysis
loses incremental_state
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--android_manifest_merger=<legacy or android>
Selects the manifest merger to use for android_binary rules. Flag to help thetransition to the Android manifest merger from the legacy merger.
default: "android"
affects outputs
loading and_analysis
loses incremental_state
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--android_manifest_merger_order=<alphabetical, alphabetical_by_configuration or dependency>
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.
default: "alphabetical"
action command_lines
execution
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--android_resource_shrinking=<true or false>
Enables resource shrinking for android_binary APKs that use ProGuard.
default: "false"
affects outputs
loading and_analysis
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--android_sdk=<build target label>
Specifies Android SDK/platform that is used to build Android applications.
default: "@bazel_tools//tools/android:sdk"
changes inputs
loading and_analysis
loses incremental_state
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--announce=<true or false>
Deprecated. No-op.
--apk_signing_method=<v1, v2 or v1_v2>
Implementation to use to sign APKs
default: "v1_v2"
action command_lines
affects outputs
loading and_analysis
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--apple_bitcode=<none, embedded_markers or embedded>
Specify the Apple bitcode mode for compile steps. Values: 'none', 'embedded_markers', 'embedded'.
--apple_compiler=<string>
The Apple target compiler. Useful for selecting variants of a toolchain (e. g. xcode-beta).
default: see description
affects outputs
loading and_analysis
loses incremental_state
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--apple_crosstool_top=<build target label>
The label of the crosstool package to be used in Apple and Objc rules and their dependencies.
default: "@bazel_tools//tools/cpp:toolchain"
loses incremental_state
changes inputs
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--apple_enable_auto_dsym_dbg=<true or false>
Whether to force enable generating debug symbol(.dSYM) file(s) for dbg builds.
default: "false"
affects outputs
action command_lines
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--apple_generate_dsym=<true or false>
Whether to generate debug symbol(.dSYM) file(s).
default: "false"
affects outputs
action command_lines
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--apple_grte_top=<build target label>
The Apple target grte_top.
default: see description
changes inputs
loading and_analysis
loses incremental_state
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--apple_sdk=<build target label>
Location of target that will provide the appropriate Apple SDK for the current build configuration.
default: see description
affects outputs
loading and_analysis
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--aspect_deps=<off, conservative or precise>
How to resolve aspect dependencies when the output format is one of {xml, proto,record}. 'off' means no aspect dependencies are resolved, 'conservative' (the default) means all declared aspect dependencies are added regardless of whether they are given the rule class of direct dependencies, 'precise' means that only those aspects are added that are possibly active given the rule class of the direct dependencies. Note that precise mode requires loading other packages to evaluate a single target thus making it slower than the other modes. Also note that even precise mode is not completely precise: the decision whether to compute an aspect is decided in the analysis phase, which is not run during 'bazel query'.
default: "conservative"
build file_semantics
aquery
cquery
query
--aspects=<comma-separated list of options>
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
--async=<true or false>
If true, output cleaning is asynchronous. When this command completes, it will be safe to execute new commands in the same client, even though the deletion may continue in the background.
default: "false"
host machine_resource_optimizations
clean
--attempt_to_print_relative_paths=<true or false>
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.
--auto_cpu_environment_group=<build target label>
Declare the environment_group to use for automatically mapping cpu values to target_environment values.
default: ""
changes inputs
loading and_analysis
experimental
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--batch=<true or false>
If set, Bazel will be run as just a client process without a server, instead of in the standard client/server mode. This is deprecated and will be removed, please prefer shutting down the server explicitly if you wish to avoid lingering servers.
default: "false"
loses incremental_state
bazel internal_configuration
deprecated
startup option
--batch_cpu_scheduling=<true or false>
Only on Linux; use 'batch' CPU scheduling for Blaze. This policy is useful for workloads that are non-interactive, but do not want to lower their nice value. See 'man 2 sched_setscheduler'. If false, then Bazel does not perform a system call.
default: "false"
host machine_resource_optimizations
startup option
--bazelrc=<string>
The location of the user .bazelrc file containing default values of Bazel options. If unspecified, Bazel uses the first .bazelrc file it finds in the following two locations: the workspace directory, then the user's home directory. Use /dev/null to disable the search for a user rc file, e.g. in release builds.
default: see description
changes inputs
startup option
--bep_publish_used_heap_size_post_build=<true or false>
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.
--bes_backend=<string>
Specifies the build event service (BES) backend endpoint as HOST or HOST: PORT. Disabled by default.
--bes_best_effort=<true or false>
BES best effort upload has been removed. The flag has no more functionality attached to it and will be removed in a future release.
--bes_keywords=<comma-separated list of options>
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.
--bes_lifecycle_events=<true or false>
Specifies whether to publish BES lifecycle events. (defaults to 'true').
--bes_outerr_buffer_size=<integer>
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.
--bes_outerr_chunk_size=<integer>
Specifies the maximal size of stdout or stderr to be sent to BEP in a single message.
--bes_results_url=<string>
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.
--bes_timeout=<An immutable length of time.>
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.
--block_for_lock=<true or false>
When --noblock_for_lock is passed, Bazel does not wait for a running command to complete, but instead exits immediately.
default: "true"
eagerness to_exit
startup option
--build=<true or false>
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.
--build_event_binary_file=<string>
If non-empty, write a varint delimited binary representation of representation of the build event protocol to that file.
--build_event_binary_file_path_conversion=<true or false>
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
--build_event_json_file=<string>
If non-empty, write a JSON serialisation of the build event protocol to that file.
--build_event_max_named_set_of_file_entries=<integer>
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.
--build_event_publish_all_actions=<true or false>
Whether all actions should be published.
--build_event_text_file=<string>
If non-empty, write a textual representation of the build event protocol to that file
--build_event_text_file_path_conversion=<true or false>
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
--build_manual_tests=<true or false>
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_zip=<tri-state (auto, yes, no)>
Build python executable zip; on on Windows, off on other platforms
--build_runfile_links=<true or false>
If true, build runfiles symlink forests for all targets. If false, write only manifests when possible.
--build_runfile_manifests=<true or false>
If true, write runfiles manifests for all targets. If false, omit them.
--build_tag_filters=<comma-separated list of options>
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'
--build_test_dwp=<true or false>
If enabled, when building C++ tests statically and with fission the .dwp file for the test binary will be automatically built as well.
default: "false"
loading and_analysis
affects outputs
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--build_tests_only=<true or false>
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.
--cache_test_results=<tri-state (auto, yes, no)>
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.
--canonicalize_policy=<true or false>
Output the canonical policy, after expansion and filtering. To keep the output clean, the canonicalized command arguments will NOT be shown when this option is set to true. Note that the command specified by -- for_command affects the filtered policy, and if none is specified, the default command is 'build'.
default: "false"
affects outputs
terminal output
canonicalize-flags
--cc_output_directory_tag=<string>
Specifies a suffix to be added to the configuration directory.
--cc_proto_library_header_suffixes=<comma-separated list of options>
Sets the prefixes of header files that a cc_proto_library creates.
default: ".pb.h"
affects outputs
loading and_analysis
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--cc_proto_library_source_suffixes=<comma-separated list of options>
Sets the prefixes of source files that a cc_proto_library creates.
default: ".pb.cc"
affects outputs
loading and_analysis
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--chart=<true or false>
If --nochart is present, do not include the task chart with --html_details. The default is --chart.
default: "true"
affects outputs
analyze-profile
--check_constraint=<string>
Check the listed constraint.
--check_licenses=<true or false>
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.
--check_tests_up_to_date=<true or false>
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
--check_third_party_targets_have_licenses=<true or false>
If true, all rules and files under //third_party must declare licenses([])
--check_up_to_date=<true or false>
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.
--check_visibility=<true or false>
If disabled, visibility errors are demoted to warnings.
--client_debug=<true or false>
If true, log debug information from the client to stderr. Changing this option will not cause the server to restart.
default: "false"
affects outputs
bazel monitoring
startup option
--collapse_duplicate_defines=<true or false>
When enabled, redundant --defines will be removed early in the build. This avoids unnecessary loss of the analysis cache for certain types of equivalent builds.
default: "false"
loading and_analysis
loses incremental_state
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--collect_code_coverage=<true or false>
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.
--color=<yes, no or auto>
Use terminal controls to colorize output going to stderr.
--combine=<string>
If present, the statistics of all given profile files will be combined and output in text/--html format to the file named in the argument. Does not output HTML task charts.
default: see description
affects outputs
analyze-profile
--combined_report=<none or lcov>
Specifies desired cumulative coverage report type. At this point only HTML and LCOV reports are supported.
--compilation_mode=<fastbuild, dbg or opt>
Specify the mode the binary will be built in. Values: 'fastbuild', 'dbg', 'opt'.
default: "fastbuild"
affects outputs
action command_lines
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--compile_one_dependency=<true or false>
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.
--compiler=<string>
The C++ compiler to use for compiling the target.
default: see description
loading and_analysis
execution
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--config=<string>
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.
--conlyopt=<string>
Additional option to pass to gcc when compiling C source files.
may be used multiple times
action command_lines
affects outputs
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--connect_timeout_secs=<integer>
The amount of time the client waits for each attempt to connect to the server
default: "30"
bazel internal_configuration
startup option
--copt=<string>
Additional options to pass to gcc.
may be used multiple times
action command_lines
affects outputs
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--coverage_report_generator=<build target label>
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'.
default: "@bazel_tools//tools/test:coverage_report_generator"
changes inputs
affects outputs
loading and_analysis
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--coverage_support=<build target label>
Location of support files that are required on the inputs of every test action that collects code coverage. Defaults to '//tools/test: coverage_support'.
default: "@bazel_tools//tools/test:coverage_support"
changes inputs
affects outputs
loading and_analysis
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--cpu=<string>
The target CPU.
--crosstool_top=<build target label>
The label of the crosstool package to be used for compiling C++ code.
default: "@bazel_tools//tools/cpp:toolchain"
loading and_analysis
changes inputs
affects outputs
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--curses=<yes, no or auto>
Use terminal cursor controls to minimize scrolling output going to stderr.
--custom_malloc=<build target label>
Specifies a custom malloc implementation. This setting overrides malloc attributes in build rules.
default: see description
changes inputs
affects outputs
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--cxxopt=<string>
Additional option to pass to gcc when compiling C++ source files.
may be used multiple times
action command_lines
affects outputs
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--debug_app
Whether to wait for the debugger before starting the app. Expands to: --start=DEBUG
--deep_execroot=<true or false>
If set, the execution root will be under $OUTPUT_BASE/execroot instead of $OUTPUT_BASE.
default: "true"
loses incremental_state
execution
startup option
--default_ios_provisioning_profile=<build target label>
--define=<'name=value' assignment>
Each --define option specifies an assignment for a build variable.
may be used multiple times
changes inputs
affects outputs
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--deleted_packages=<comma-separated list of package names>
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.
--desugar_for_android=<true or false>
Whether to desugar Java 8 bytecode before dexing.
default: "true"
affects outputs
loading and_analysis
loses incremental_state
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--device=<string>
The adb device serial number. If not specified, the first device will be used.
default: ""
action command_lines
mobile-install
--device_debug_entitlements=<true or false>
If set, and compilation mode is not 'opt', objc apps will include debug entitlements when signing.
--discard_analysis_cache=<true or false>
Discard the analysis cache immediately after the analysis phase completes. Reduces memory usage by ~10%, but makes further incremental builds slower.
--disk_cache=<path>
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.
--distdir=<path>
Additional places to search for archives before accessing the network to download them.
may be used multiple times
bazel internal_configuration
aquery
build
clean
coverage
cquery
fetch
info
mobile-install
print_action
query
run
sync
test
--distinct_host_configuration=<true or false>
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.
default: "true"
loses incremental_state
bazel internal_configuration
loading and_analysis
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--dump=<text, raw, text-unsorted or raw-unsorted>
output full profile data dump either in human-readable 'text' format or script-friendly 'raw' format, either sorted or unsorted.
default: see description
affects outputs
analyze-profile
--dynamic_mode=<off, default or fully>
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.
default: "default"
loading and_analysis
affects outputs
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--embed_label=<string>
Embed source control revision or release label in binary
--enable_apple_binary_native_protos=<true or false>
If set, apple_binary will generate and link objc protos into the output binary.
default: "true"
affects outputs
incompatible change
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--enable_fdo_profile_absolute_path=<true or false>
If set, use of fdo_absolute_profile_path will raise an error.
--enable_runfiles=<tri-state (auto, yes, no)>
Enable runfiles symlink tree; By default, it's off on Windows, on on other platforms.
--enabled_toolchain_types=<build target label>
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.
--enforce_constraints=<true or false>
Checks the environments each target is compatible with and reports errors if any target has dependencies that don't support the same environments
--expand_configs_in_place=<true or false>
Changed the expansion of --config flags to be done in-place, as opposed to in a fixed point expansion between normal rc options and command-line specified options.
default: "true"
no op
deprecated
startup option
--expand_test_suites=<true or false>
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.
--experimental_action_listener=<build target label>
Use action_listener to attach an extra_action to existing build actions.
may be used multiple times
execution
experimental
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--experimental_allow_android_library_deps_without_srcs=<true or false>
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.
default: "false"
eagerness to_exit
loading and_analysis
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--experimental_android_compress_java_resources=<true or false>
Compress Java resources in APKs
default: "false"
affects outputs
loading and_analysis
experimental
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--experimental_android_databinding_v2=<true or false>
Use android databinding v2
default: "false"
affects outputs
loading and_analysis
loses incremental_state
experimental
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--experimental_android_resource_shrinking=<true or false>
Enables resource shrinking for android_binary APKs that use ProGuard.
default: "false"
affects outputs
loading and_analysis
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--experimental_android_rewrite_dexes_with_rex=<true or false>
use rex tool to rewrite dex files
default: "false"
affects outputs
loading and_analysis
loses incremental_state
experimental
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--experimental_android_throw_on_resource_conflict=<true or false>
If passed, resource merge conflicts will be treated as errors instead of warnings
default: "false"
eagerness to_exit
loading and_analysis
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--experimental_android_use_parallel_dex2oat=<true or false>
Use dex2oat in parallel to possibly speed up android_test.
default: "false"
loading and_analysis
host machine_resource_optimizations
experimental
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--experimental_build_event_json_file_path_conversion=<true or false>
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
--experimental_build_event_upload_strategy=<string>
Selects how to upload artifacts referenced in the build event protocol.
--experimental_check_desugar_deps=<true or false>
Whether to double-check correct desugaring at Android binary level.
default: "true"
eagerness to_exit
loading and_analysis
experimental
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--experimental_desugar_java8_libs=<true or false>
Whether to include supported Java 8 libraries in apps for legacy devices.
default: "false"
affects outputs
loading and_analysis
loses incremental_state
experimental
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--experimental_docker_image=<string>
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.
--experimental_docker_privileged=<true or false>
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.
--experimental_docker_use_customized_images=<true or false>
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.
--experimental_docker_verbose=<true or false>
If enabled, Bazel will print more verbose messages about the Docker sandbox strategy.
--experimental_enable_android_migration_apis=<true or false>
If set to true, enables the APIs required to support the Android Starlark migration.
--experimental_enable_docker_sandbox=<true or false>
Enable Docker-based sandboxing. This option has no effect if Docker is not installed.
--experimental_enable_objc_cc_deps=<true or false>
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.
default: "true"
loading and_analysis
incompatible change
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--experimental_execution_log_file=<string>
Log the executed spawns into this file as delimited Spawn protos.
--experimental_external_repositories=<true or false>
Use external repositories for improved stability and speed when available.
--experimental_extra_action_filter=<comma-separated list of regex expressions with prefix '-' specifying excluded paths>
Filters set of targets to schedule extra_actions for.
--experimental_extra_action_top_level_only=<true or false>
Only schedules extra_actions for top level targets.
--experimental_generate_json_trace_profile=<true or false>
If enabled, Bazel profiles the build and writes a JSON-format profile into a file in the output base.
--experimental_guard_against_concurrent_changes=<true or false>
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.
--experimental_import_deps_checking=<off, warning or error>
When enabled, check whether the dependencies of an aar_import are complete. This enforcement can break the build, or can just result in warnings.
--experimental_inmemory_dotd_files=<true or false>
If enabled, C++ .d files will be passed through in memory directly from the remote build nodes instead of being written to disk.
default: "false"
loading and_analysis
execution
affects outputs
experimental
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--experimental_inmemory_jdeps_files=<true or false>
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.
default: "false"
loading and_analysis
execution
affects outputs
experimental
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--experimental_interleave_loading_and_analysis=<true or false>
No-op.
--experimental_j2objc_header_map=<true or false>
Whether to generate J2ObjC header map in parallel of J2ObjC transpilation.
--experimental_java_classpath=<off, javabuilder or bazel>
Enables reduced classpaths for Java compilations.
--experimental_java_proto_add_allowed_public_imports=<true or false>
If true, add --allowed_public_imports to the java compile actions.
default: "false"
affects outputs
loading and_analysis
experimental
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--experimental_json_trace_compression=<true or false>
If enabled, Bazel compresses the JSON-format profile with gzip.
--experimental_link_compile_output_separately=<true or false>
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.
default: "false"
loading and_analysis
affects outputs
experimental
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--experimental_local_execution_delay=<integer>
How many milliseconds should local execution be delayed, if remote execution was faster during a build at least once?
--experimental_local_memory_estimate=<true or false>
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.
--experimental_multi_cpu=<comma-separated list of options>
This flag allows specifying multiple target CPUs. If this is specified, the --cpu option is ignored.
may be used multiple times
affects outputs
experimental
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--experimental_multi_threaded_digest=<true or false>
Whether to always compute MD5 digests of files with multiple threads. Might improve performance when using an SSD.
--experimental_objc_enable_module_maps=<true or false>
Enables module map generation and interpretation.
--experimental_objc_fastbuild_options=<comma-separated list of options>
Uses these strings as objc fastbuild compiler options.
--experimental_objc_header_thinning=<true or false>
If set then ObjcCompile actions will have their action inputs reduced by running a tool to detect which headers are actually required for compilation.
default: "false"
changes inputs
loading and_analysis
experimental
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--experimental_omitfp=<true or false>
If true, use libunwind for stack unwinding, and compile with -fomit-frame- pointer and -fasynchronous-unwind-tables.
default: "false"
action command_lines
affects outputs
experimental
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--experimental_oom_more_eagerly=<true or false>
If set, attempt to detect Java heap OOM conditions and exit before thrashing. Only honored when --batch is also passed. In some cases, builds that previously succeeded may OOM if they were close to OOMing before. Deprecated: Use the command argument -- experimental_oom_more_eagerly_threshold instead.
default: "false"
loses incremental_state
eagerness to_exit
startup option
--experimental_oom_more_eagerly_threshold=<integer>
If this flag is set, Bazel will OOM if, after two full GC's, more than this percentage of the (old gen) heap is still occupied. Deprecated: Use the command argument --experimental_oom_more_eagerly_threshold instead.
default: "100"
loses incremental_state
eagerness to_exit
applies to all commands
--experimental_persistent_javac
Enable the experimental persistent Java compiler. Expands to: --strategy=Javac=worker --strategy=JavaIjar=local -- strategy=JavaDeployJar=local --strategy=JavaSourceJar=local -- strategy=Turbine=local
--experimental_platforms_api=<true or false>
If set to true, enables a number of platform-related Starlark APIs useful for debugging.
--experimental_post_profile_started_event=<true or false>
If set, Bazel will post the ProfilerStartedEvent including the path to the profile.
--experimental_profile_additional_tasks=<phase, action, __action_builder, __action_submit, action_check, __action_execute, action_lock, action_release, __action_graph, action_update, action_complete, info, __exception, create_package, __package_validity_check, __spawn, remote_execution, local_execution, scanner, local_parse, upload_time, process_time, remote_queue, remote_setup, fetch, vfs_stat, vfs_dir, vfs_readlink, vfs_md5, vfs_xattr, vfs_delete, vfs_open, vfs_read, vfs_write, vfs_glob, vfs_vmfs_stat, vfs_vmfs_dir, vfs_vmfs_read, wait, __configured_target, thread_name, __test, skyframe_eval, skyfunction, critical_path, critical_path_component, handle_gc_notification, local_cpu_usage, __inclusion_parse, __process_scan, __loop_output_artifacts, __locate_relative, __construct_include_paths, __parse_and_hints_results, __process_results_and_enqueue, starlark_parser, starlark_user_fn, starlark_builtin_fn, starlark_user_compiled_fn, action_fs_staging or unknown>
Specifies additional profile tasks to be included in the profile.
--experimental_profile_cpu_usage=<true or false>
If set, Bazel will measure cpu usage and add it to the JSON profile.
--experimental_proto_extra_actions=<true or false>
Run extra actions for alternative Java api versions in a proto_library.
default: "false"
affects outputs
loading and_analysis
experimental
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--experimental_remote_download_outputs=<all or minimal>
If set to 'minimal' doesn't download any remote build outputs to the local machine, except the ones required by local actions. This option can significantly reduce build times if network bandwidth is a bottleneck.
--experimental_remote_grpc_log=<string>
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).
--experimental_remote_retry=<true or false>
Whether to retry transient remote execution/cache errors.
--experimental_remote_retry_jitter=<double>
The random factor to apply to retry delays on transient errors.
--experimental_remote_retry_max_attempts=<integer>
The maximum number of attempts to retry a transient error.
--experimental_remote_retry_max_delay_millis=<long integer>
The maximum delay before retrying a transient error.
--experimental_remote_retry_multiplier=<double>
The multiplier by which to increase the retry delay on transient errors.
--experimental_remote_retry_start_delay_millis=<long integer>
The initial delay before retrying a transient error.
--experimental_repository_cache_hardlinks=<true or false>
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.
--experimental_repository_hash_file=<string>
If non-empty, specifies a file containing a resolved value, against which the repository directory hashes should be verified
--experimental_repository_resolved_file=<string>
If non-empty, write a Skylark value with the resolved information of all Starlark repository rules that were executed.
--experimental_resolved_file_instead_of_workspace=<string>
If non-empty read the specified resolved file instead of the WORKSPACE file
--experimental_restrict_named_params=<true or false>
If set to true, restricts a number of Starlark built-in function parameters to be only specifiable positionally (and not by keyword).
--experimental_sandbox_base=<string>
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.
--experimental_sandbox_default_allow_network=<true or false>
Allow network access by default for actions.
--experimental_sandboxfs_map_symlink_targets=<true or false>
If true, maps the targets of symbolic links specified as action inputs into the sandbox. This feature exists purely to workaround buggy rules that do not do this on their own and should be removed once all such rules are fixed.
--experimental_sandboxfs_path=<string>
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.
--experimental_scale_timeouts=<double>
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
default: "1.0"
bazel internal_configuration
experimental
aquery
build
clean
coverage
cquery
fetch
info
mobile-install
print_action
query
run
sync
test
--experimental_slim_json_profile=<true or false>
Slims down the size of the JSON profile by merging events if the profile gets too large.
--experimental_spawn_scheduler
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
--experimental_split_xml_generation=<true or false>
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.
--experimental_starlark_config_transitions=<true or false>
If set to true, enables creation of configuration transition objects (the `transition()` function) in Starlark.
--experimental_strict_fileset_output=<true or false>
If this option is enabled, filesets will treat all output artifacts as regular files. They will not traverse directories or be sensitive to symlinks.
--experimental_strict_java_deps=<off, warn, error, strict or default>
If true, checks that a Java target explicitly declares all directly used targets as dependencies.
default: "default"
build file_semantics
eagerness to_exit
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--experimental_ui_deduplicate=<true or false>
Make the UI deduplicate messages to have a cleaner scroll-back log.
--experimental_ui_limit_console_output=<integer>
Number of bytes to which the UI will limit its output (non-positive values indicate unlimited). Once the limit is approaching, the UI will try hard to limit in a meaningful way, but will ultimately just drop all output.
--experimental_use_llvm_covmap=<true or false>
If specified, Bazel will generate llvm-cov coverage map information rather than gcov when collect_code_coverage is enabled.
default: "false"
changes inputs
affects outputs
loading and_analysis
experimental
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--experimental_use_sandboxfs=<tri-state (auto, yes, no)>
Use sandboxfs to create the actions' execroot directories instead of building a symlink tree. If "yes", the binary provided by --experimental_sandboxfs_path must be valid and correspond to a supported version of sandboxfs. If "auto", the binary may be missing or not compatible.
--experimental_verify_repository_rules=<string>
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.
--experimental_workspace_rules_log_file=<string>
Log certain Workspace Rules events into this file as delimited WorkspaceEvent protos.
--explain=<path>
Causes the build system to explain each executed step of the build. The explanation is written to the specified log file.
--explicit_java_test_deps=<true or false>
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.
--expunge=<true or false>
If true, clean removes the entire working tree for this bazel instance, which includes all bazel-created temporary and build output files, and stops the bazel server if it is running.
default: "false"
host machine_resource_optimizations
clean
--expunge_async
If specified, clean asynchronously removes the entire working tree for this bazel instance, which includes all bazel-created temporary and build output files, and stops the bazel server if it is running. When this command completes, it will be safe to execute new commands in the same client, even though the deletion may continue in the background. Expands to: --expunge --async
host machine_resource_optimizations
clean
--extra_entitlements=<build target label>
Location of a .entitlements file that is merged into any iOS signing action in this build.
--extra_execution_platforms=<comma-separated list of options>
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().
--extra_toolchains=<comma-separated list of options>
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().
may be used multiple times
affects outputs
changes inputs
loading and_analysis
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--fat_apk_cpu=<comma-separated list of options>
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.
default: "armeabi-v7a"
affects outputs
loading and_analysis
loses incremental_state
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--fdo_instrument=<string>
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
--fdo_optimize=<string>
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.
--fdo_prefetch_hints=<build target label>
Use cache prefetch hints.
--fdo_profile=<build target label>
The fdo_profile representing the profile to be used for optimization.
--features=<string>
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.
may be used multiple times
changes inputs
affects outputs
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--fission=<set of compilation modes>
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.
default: "no"
loading and_analysis
action command_lines
affects outputs
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--flaky_test_attempts=<positive integer, the string "default", or test_regex@attempts. This flag may be passed more than once>
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).
--for_command=<string>
The command for which the options should be canonicalized.
default: "build"
affects outputs
terminal output
canonicalize-flags
--force_experimental_external_repositories=<true or false>
Forces --experimental_external_repositories.
--force_pic=<true or false>
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").
default: "false"
loading and_analysis
affects outputs
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--force_python=<PY2 or PY3>
Deprecated alias for `--python_version`. Disabled by `-- incompatible_remove_old_python_version_api`.
default: see description
loading and_analysis
affects outputs
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--genrule_strategy=<comma-separated list of options>
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.
--gnu_format=<true or false>
If set, write the version to stdout using the conventions described in the GNU standards.
default: "false"
affects outputs
execution
version
--google_auth_scopes=<comma-separated list of options>
A comma-separated list of Google Cloud authentication scopes.
--google_credentials=<string>
Specifies the file to get authentication credentials from. See https://cloud.google.com/docs/authentication for details.
--google_default_credentials=<true or false>
Whether to use 'Google Application Default Credentials' for authentication. See https://cloud.google.com/docs/authentication for details. Disabled by default.
--graph:conditional_edges_limit=<integer>
The maximum number of condition labels to show. -1 means no truncation and 0 means no annotation. This option is only applicable to --output=graph.
default: "4"
terminal output
query
--graph:factored=<true or false>
If true, then the graph will be emitted 'factored', i.e. topologically- equivalent nodes will be merged together and their labels concatenated. This option is only applicable to --output=graph.
default: "true"
terminal output
query
--graph:node_limit=<integer>
The maximum length of the label string for a graph node in the output. Longer labels will be truncated; -1 means no truncation. This option is only applicable to --output=graph.
default: "512"
terminal output
query
--grte_top=<label>
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.
default: see description
action command_lines
affects outputs
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--help_verbosity=<long, medium or short>
Select the verbosity of the help command.
default: "medium"
affects outputs
terminal output
help
--high_priority_workers=<string>
Mnemonics of workers to run with high priority. When high priority workers are running all other workers are throttled.
--home_rc=<true or false>
Whether or not to look for the home bazelrc file at $HOME/.bazelrc
default: "true"
changes inputs
startup option
--host_compilation_mode=<fastbuild, dbg or opt>
Specify the mode the tools used during the build will be built in. Values: 'fastbuild', 'dbg', 'opt'.
default: "opt"
affects outputs
action command_lines
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--host_compiler=<string>
The C++ compiler to use for host compilation. It is ignored if -- host_crosstool_top is not set.
default: see description
loading and_analysis
execution
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--host_conlyopt=<string>
Additional option to pass to gcc when compiling C source files for host tools.
may be used multiple times
action command_lines
affects outputs
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--host_copt=<string>
Additional options to pass to gcc for host tools.
may be used multiple times
action command_lines
affects outputs
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--host_cpu=<string>
The host CPU.
--host_crosstool_top=<build target label>
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.
default: see description
loading and_analysis
changes inputs
affects outputs
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--host_cxxopt=<string>
Additional options to pass to gcc for host tools.
may be used multiple times
action command_lines
affects outputs
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--host_deps=<true or false>
Query: If disabled, dependencies on 'host configuration' targets will not be included in the dependency graph over which the query operates. A 'host configuration' dependency edge, such as the one from any 'proto_library' rule to the Protocol Compiler, usually points to a tool executed during the build (on the host machine) rather than a part of the same 'target' program. Cquery: If disabled, filters out all configured targets which cross a host transition from the top-level target that discovered this configured target. That means if the top-level target is in the target configuration, only configured targets also in the target configuration will be returned. If the top-level target is in the host configuration, only host configured targets will be returned.
default: "true"
build file_semantics
aquery
cquery
query
--host_force_python=<PY2 or PY3>
Overrides the Python version for the host configuration. Can be "PY2" or "PY3".
default: see description
loading and_analysis
affects outputs
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--host_grte_top=<label>
If specified, this setting overrides the libc top-level directory (-- grte_top) for the host configuration.
default: see description
action command_lines
affects outputs
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--host_java_launcher=<build target label>
The Java launcher used by tools that are executed during a build.
--host_java_toolchain=<build target label>
The Java toolchain used to build tools that are executed during a build.
default: "@bazel_tools//tools/jdk:remote_toolchain"
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--host_javabase=<build target label>
JAVABASE used for the host JDK. This is the java_runtime which is used to execute tools during a build.
--host_javacopt=<string>
Additional options to pass to javac when building tools that are executed during a build.
--host_jvm_args=<string>
Flags to pass to the JVM executing Blaze.
may be used multiple times
startup option
--host_jvm_debug
Convenience option to add some additional JVM startup flags, which cause the JVM to wait during startup until you connect from a JDWP-compliant debugger (like Eclipse) to port 5005. Expands to: --host_jvm_args=-Xdebug --host_jvm_args=-Xrunjdwp: transport=dt_socket,server=y,address=5005
--host_jvm_profile=<string>
Convenience option to add some profiler/debugger-specific JVM startup flags. Bazel has a list of known values that it maps to hard-coded JVM startup flags, possibly searching some hardcoded paths for certain files.
default: ""
startup option
--host_linkopt=<string>
Additional option to pass to gcc when linking host tools.
may be used multiple times
action command_lines
affects outputs
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--host_platform=<build target label>
The label of a platform rule that describes the host system.
default: ""
affects outputs
changes inputs
loading and_analysis
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--host_swiftcopt=<string>
Additional options to pass to swiftc for host tools.
may be used multiple times
action command_lines
affects outputs
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--html=<true or false>
If present, an HTML file visualizing the tasks of the profiled build is created. The name of the html file is the name of the profile file plus '. html'.
default: "false"
affects outputs
analyze-profile
--html_details=<true or false>
If --html_details is present, the task diagram contains all tasks of the profile and performance statistics on user-defined and built-in Skylark functions. If --nohtml_details is present, an aggregated diagram is generated. The default is to generate an aggregated diagram.
default: "false"
affects outputs
analyze-profile
--html_histograms=<true or false>
If --html_histograms and --html_details is present, the HTML output will display histograms for Skylark functions clicked in the statistics table. This will increase file size massively.
default: "false"
affects outputs
analyze-profile
--html_pixels_per_second=<integer>
Defines the scale of the time axis of the task diagram. The unit is pixels per second. Default is 50 pixels per second.
default: "50"
affects outputs
analyze-profile
--idle_server_tasks=<true or false>
Run System.gc() when the server is idle
default: "true"
loses incremental_state
host machine_resource_optimizations
startup option
--iff_heap_size_greater_than=<integer>
Iff non-zero, then shutdown will only shut down the server if the total memory (in MB) consumed by the JVM exceeds this value.
default: "0"
loses incremental_state
eagerness to_exit
shutdown
--ignore_all_rc_files=<true or false>
Disables all rc files, regardless of the values of other rc-modifying flags, even if these flags come later in the list of startup options.
default: "false"
changes inputs
startup option
--ignore_unsupported_sandboxing=<true or false>
Do not print a warning when sandboxed execution is not supported on this system.
--implicit_deps=<true or false>
If enabled, implicit dependencies will be included in the dependency graph over which the query operates. An implicit dependency is one that is not explicitly specified in the BUILD file but added by bazel.
default: "true"
build file_semantics
aquery
cquery
query
--include_artifacts=<true or false>
Includes names of the action inputs and outputs in the output (potentially large).
default: "true"
terminal output
aquery
--include_aspects=<true or false>
Whether to include aspect generated actions in the output.
default: "false"
terminal output
aquery
--include_commandline=<true or false>
Includes the content of the action command lines in the output (potentially large).
default: "true"
terminal output
aquery
--include_param_files=<true or false>
Include the content of the param files used in the command (potentially large). Note: Enabling this flag will automatically enable the -- include_commandline flag.
default: "false"
terminal output
aquery
--incompatible_allow_python_version_transitions=<true or false>
If true, Python rules use the new PY2/PY3 version semantics. For more information, see the documentation for `py_binary`'s `python_version` attribute.
default: "true"
loading and_analysis
incompatible change
triggered by_all_incompatible_changes
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--incompatible_bzl_disallow_load_after_statement=<true or false>
If set to true, all `load` must be called at the top of .bzl files, before any other statement.
--incompatible_cc_coverage=<true or false>
If specified, Bazel will use gcov to collect code coverage for C++ test targets. This option only works for gcc compilation.
default: "true"
changes inputs
affects outputs
loading and_analysis
incompatible change
triggered by_all_incompatible_changes
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--incompatible_depset_is_not_iterable=<true or false>
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.
--incompatible_depset_union=<true or false>
If set to true, depset union using `+`, `|` or `.union` are forbidden. Use the `depset` constructor instead.
--incompatible_disable_crosstool_file=<true or false>
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.
default: "true"
loading and_analysis
triggered by_all_incompatible_changes
incompatible change
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--incompatible_disable_deprecated_attr_params=<true or false>
If set to true, disable the deprecated parameters 'single_file' and 'non_empty' on attribute definition methods, such as attr.label().
--incompatible_disable_expand_if_all_available_in_flag_set=<true or false>
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).
default: "true"
loading and_analysis
incompatible change
triggered by_all_incompatible_changes
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--incompatible_disable_objc_provider_resources=<true or false>
If set to true, disallow use of deprecated resource fields on the Objc provider.
--incompatible_disable_third_party_license_checking=<true or false>
If true, disables all license checking logic. This overrides -- check_third_party_targets_have_licenses
--incompatible_disallow_dict_plus=<true or false>
If set to true, the `+` becomes disabled for dicts.
--incompatible_disallow_filetype=<true or false>
If set to true, function `FileType` is not available.
--incompatible_disallow_legacy_java_provider=<true or false>
If set to true, usages of old .java provider are disallowed.
--incompatible_disallow_legacy_javainfo=<true or false>
If set to true, old-style JavaInfo provider construction is disallowed.
--incompatible_disallow_legacy_py_provider=<true or false>
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.
default: "true"
loading and_analysis
incompatible change
triggered by_all_incompatible_changes
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--incompatible_disallow_load_labels_to_cross_package_boundaries=<true or false>
If set to true, the label argument to 'load' cannot cross a package boundary.
--incompatible_disallow_native_in_build_file=<true or false>
If set to true, the native module is not accessible in BUILD files. Use for example `cc_library` instead of `native.cc_library`.
--incompatible_disallow_old_style_args_add=<true or false>
If set to true, vectorized calls to Args#add are disallowed.
--incompatible_disallow_struct_provider_syntax=<true or false>
If set to true, rule implementation functions may not return a struct. They must instead return a list of provider instances.
--incompatible_do_not_split_linking_cmdline=<true or false>
When true, Bazel no longer modifies command line flags used for linking, and also doesn't selectively decide which flags go to the param file and which don't. See https://github.com/bazelbuild/bazel/issues/7670 for details.
--incompatible_dont_enable_host_nonhost_crosstool_features=<true or false>
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).
default: "false"
loading and_analysis
incompatible change
triggered by_all_incompatible_changes
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--incompatible_expand_directories=<true or false>
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.
--incompatible_list_based_execution_strategy_selection=<true or false>
See https://github.com/bazelbuild/bazel/issues/7480
default: "false"
execution
incompatible change
triggered by_all_incompatible_changes
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--incompatible_merge_genfiles_directory=<true or false>
If true, the genfiles directory is folded into the bin directory.
default: "true"
affects outputs
incompatible change
triggered by_all_incompatible_changes
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--incompatible_new_actions_api=<true or false>
If set to true, the API to create actions is only available on `ctx. actions`, not on `ctx`.
--incompatible_no_attr_license=<true or false>
If set to true, disables the function `attr.license`.
--incompatible_no_output_attr_default=<true or false>
If set to true, disables the `default` parameter of the `attr.output` and `attr.output_list` attribute definition functions.
--incompatible_no_support_tools_in_action_inputs=<true or false>
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`.
--incompatible_no_target_output_group=<true or false>
If set to true, disables the output_group field of the 'Target' Starlark type.
--incompatible_no_transitive_loads=<true or false>
If set to true, only symbols explicitly defined in the file can be loaded; symbols introduced by load are not implicitly re-exported.
--incompatible_py2_outputs_are_suffixed=<true or false>
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`.
default: "true"
affects outputs
incompatible change
triggered by_all_incompatible_changes
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--incompatible_py3_is_default=<true or false>
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`.
default: "true"
loading and_analysis
affects outputs
incompatible change
triggered by_all_incompatible_changes
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--incompatible_remap_main_repo=<true or false>
If set to true, will treat references to '@<main repo name>' the same as '@'.
--incompatible_remote_symlinks=<true or false>
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.
default: "true"
execution
incompatible change
triggered by_all_incompatible_changes
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--incompatible_remove_cpu_and_compiler_attributes_from_cc_toolchain=<true or false>
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).
default: "true"
loading and_analysis
incompatible change
triggered by_all_incompatible_changes
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--incompatible_remove_legacy_whole_archive=<true or false>
If true, Bazel will not link library dependencies as whole archive by default (see https://github.com/bazelbuild/bazel/issues/7362 for migration instructions).
default: "false"
loading and_analysis
incompatible change
triggered by_all_incompatible_changes
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--incompatible_remove_local_resources=<true or false>
Deprecate local_resources in favor of --local_ram_resources and -- local_cpu_resources.
default: "false"
execution
incompatible change
triggered by_all_incompatible_changes
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--incompatible_remove_native_maven_jar=<true or false>
If set to true, the native maven_jar rule is disabled; only the Starlark version will be available
--incompatible_remove_old_python_version_api=<true or false>
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`.
default: "true"
loading and_analysis
incompatible change
triggered by_all_incompatible_changes
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--incompatible_require_ctx_in_configure_features=<true or false>
If true, Bazel will require 'ctx' parameter in to cc_common. configure_features (see https://github.com/bazelbuild/bazel/issues/7793 for more information).
default: "false"
loading and_analysis
incompatible change
triggered by_all_incompatible_changes
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--incompatible_strict_action_env=<true or false>
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.
default: "false"
loading and_analysis
incompatible change
triggered by_all_incompatible_changes
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--incompatible_strict_objc_module_maps=<true or false>
Propagates Objective-C module maps only to direct dependencies in the 'objc' provider, not to all transitive dependencies.
default: "false"
changes inputs
loading and_analysis
incompatible change
triggered by_all_incompatible_changes
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--incompatible_string_join_requires_strings=<true or false>
If set to true, the argument of `string.join` must be an iterable whose elements are strings. If set to false, elements are first converted to string. See https://github.com/bazelbuild/bazel/issues/7802
--incompatible_symlinked_sandbox_expands_tree_artifacts_in_runfiles_tree=<true or false>
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.
default: "true"
execution
triggered by_all_incompatible_changes
incompatible change
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--incompatible_use_aapt2_by_default=<true or false>
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
default: "false"
loses incremental_state
affects outputs
incompatible change
triggered by_all_incompatible_changes
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--incompatible_use_python_toolchains=<true or false>
If set to true, executable native Python rules will use the Python runtime specified by the Python toolchain, rather than the runtime given by legacy flags like --python_top.
default: "false"
loading and_analysis
incompatible change
triggered by_all_incompatible_changes
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--incompatible_use_toolchain_providers_in_java_common=<true or false>
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.
--incompatible_windows_escape_jvm_flags=<true or false>
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
default: "true"
action command_lines
affects outputs
incompatible change
triggered by_all_incompatible_changes
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--incompatible_windows_native_test_wrapper=<true or false>
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.
default: "false"
loading and_analysis
test runner
incompatible change
triggered by_all_incompatible_changes
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--incompatible_windows_style_arg_escaping=<true or false>
On Linux/macOS/non-Windows: no-op. On Windows: if true, then subprocess arguments are escaped Windows-style. When false, the arguments are escaped Bash-style. The Bash-style is buggy, the Windows-style is correct. See https://github.com/bazelbuild/bazel/issues/7122
default: "false"
action command_lines
execution
incompatible change
triggered by_all_incompatible_changes
startup option
--incremental=<true or false>
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.
default: "false"
loading and_analysis
mobile-install
--incremental_dexing=<true or false>
Does most of the work for dexing separately for each Jar file.
default: "true"
affects outputs
loading and_analysis
loses incremental_state
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--incremental_install_verbosity=<string>
The verbosity for incremental install. Set to 1 for debug logging.
default: ""
bazel monitoring
mobile-install
--instrument_test_targets=<true or false>
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.
--instrumentation_filter=<comma-separated list of regex expressions with prefix '-' specifying excluded paths>
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.
default: "-/javatests[/:],-/test/java[/:]"
affects outputs
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--interface_shared_objects=<true or false>
Use interface shared objects if supported by the toolchain. All ELF toolchains currently support this setting.
default: "true"
loading and_analysis
affects outputs
affects outputs
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--invocation_policy=<string>
Applies an invocation policy to the options to be canonicalized.
default: ""
affects outputs
terminal output
canonicalize-flags
--io_nice_level=<integer>
Only on Linux; set a level from 0-7 for best-effort IO scheduling using the sys_ioprio_set system call. 0 is highest priority, 7 is lowest. The anticipatory scheduler may only honor up to priority 4. If set to a negative value, then Bazel does not perform a system call.
default: "-1"
host machine_resource_optimizations
startup option
--ios_cpu=<string>
Specifies to target CPU of iOS compilation.
--ios_memleaks=<true or false>
Enable checking for memory leaks in ios_test targets.
--ios_minimum_os=<dotted version (for example '2.3' or '3.3alpha2.4')>
Minimum compatible iOS version for target simulators and devices.
default: see description
loses incremental_state
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--ios_multi_cpus=<comma-separated list of options>
Comma-separated list of architectures to build an ios_application with. The result is a universal binary containing all specified architectures.
default: ""
loses incremental_state
loading and_analysis
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--ios_sdk_version=<dotted version (for example '2.3' or '3.3alpha2.4')>
Specifies the version of the iOS SDK to use to build iOS applications.
default: see description
loses incremental_state
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--ios_signing_cert_name=<string>
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).
--ios_simulator_device=<string>
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.
--ios_simulator_version=<dotted version (for example '2.3' or '3.3alpha2.4')>
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.
--j2objc_translation_flags=<comma-separated list of options>
Additional options to pass to the J2ObjC tool.
--java_debug
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
--java_deps=<true or false>
Generate dependency information (for now, compile-time classpath) per Java target.
--java_header_compilation=<true or false>
Compile ijars directly from source.
--java_launcher=<build target label>
The Java launcher to use when building Java binaries. The "launcher" attribute overrides this flag.
--java_toolchain=<build target label>
The name of the toolchain rule for Java.
default: "@bazel_tools//tools/jdk:remote_toolchain"
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--javabase=<build target label>
JAVABASE used for the JDK invoked by Blaze. This is the java_runtime which will be used to execute external Java commands.
--javacopt=<string>
Additional options to pass to javac.
--jobs=<integer, or a keyword ("auto", "HOST_CPUS", "HOST_RAM"), optionally followed by an operation ([-|*]<float>) eg. "auto", "HOST_CPUS*.5">
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.
default: "auto"
host machine_resource_optimizations
execution
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--jvmopt=<string>
Additional options to pass to the Java VM. These options will get added to the VM startup options of each java_binary target.
--keep_going=<true or false>
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.
--keep_state_after_build=<true or false>
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.
--legacy_external_runfiles=<true or false>
If true, build runfiles symlink forests for external repositories under . runfiles/wsname/external/repo (in addition to .runfiles/repo).
--legacy_important_outputs=<true or false>
Use this to suppress generation of the legacy important_outputs field in the TargetComplete event.
--legacy_whole_archive=<true or false>
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.
default: "true"
action command_lines
affects outputs
deprecated
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--line_terminator_null=<true or false>
Whether each format is terminated with \0 instead of newline.
default: "false"
terminal output
query
--linkopt=<string>
Additional option to pass to gcc when linking.
may be used multiple times
action command_lines
affects outputs
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--loading_phase_threads=<integer, or a keyword ("auto", "HOST_CPUS", "HOST_RAM"), optionally followed by an operation ([-|*]<float>) eg. "auto", "HOST_CPUS*.5">
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.
--local_cpu_resources=<integer, or "HOST_CPUS", optionally followed by [-|*]<float>.>
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.
--local_ram_resources=<integer, or "HOST_RAM", optionally followed by [-|*]<float>.>
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.
--local_resources=<comma-separated available amount of RAM (in MB), CPU (in cores) and available I/O (1.0 being average workstation)>
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.
--local_termination_grace_seconds=<integer>
Time to wait between terminating a local process due to timeout and forcefully shutting it down.
--local_test_jobs=<integer, or a keyword ("auto", "HOST_CPUS", "HOST_RAM"), optionally followed by an operation ([-|*]<float>) eg. "auto", "HOST_CPUS*.5">
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.
--long
Show full description of each option, instead of just its name. Expands to: --help_verbosity=long
affects outputs
terminal output
help
--ltobackendopt=<string>
Additional option to pass to the LTO backend step (under -- features=thin_lto).
may be used multiple times
action command_lines
affects outputs
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--ltoindexopt=<string>
Additional option to pass to the LTO indexing step (under -- features=thin_lto).
may be used multiple times
action command_lines
affects outputs
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--macos_cpus=<comma-separated list of options>
Comma-separated list of architectures for which to build Apple macOS binaries.
default: "x86_64"
loses incremental_state
loading and_analysis
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--macos_minimum_os=<dotted version (for example '2.3' or '3.3alpha2.4')>
Minimum compatible macOS version for targets.
default: see description
loses incremental_state
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--macos_qos_class=<string>
Sets the QoS service class of the bazel server when running on macOS. This flag has no effect on all other platforms but is supported to ensure rc files can be shared among them without changes. Possible values are: user-interactive, user-initiated, default, utility, and background.
default: "default"
host machine_resource_optimizations
startup option
--macos_sdk_version=<dotted version (for example '2.3' or '3.3alpha2.4')>
Specifies the version of the macOS SDK to use to build macOS applications.
default: see description
loses incremental_state
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--materialize_param_files=<true or false>
Writes intermediate parameter files to output tree even when using remote action execution. Useful when debugging actions.
--max_config_changes_to_show=<integer>
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.
--max_idle_secs=<integer>
The number of seconds the build server will wait idling before shutting down. Zero means that the server will never shutdown.
default: "10800"
eagerness to_exit
loses incremental_state
startup option
--memory_profile_stable_heap_parameters=<two integers, separated by a comma>
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.
--message_translations=<string>
The message translations used for translating messages in Java targets.
--minimum_os_version=<string>
The minimum OS version which your compilation targets.
default: see description
loading and_analysis
affects outputs
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--mode=<classic, classic_internal_test_do_not_use or skylark>
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.
default: "classic"
loading and_analysis
execution
incompatible change
mobile-install
--modify_execution_info=<regex=[+-]key,regex=[+-]key,...>
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.
default: ""
execution
affects outputs
loading and_analysis
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--noorder_results
Output the results in dependency-ordered (default) or unordered fashion. The unordered output is faster but only supported when --output is not minrank, maxrank, or graph. Expands to: --order_output=no
terminal output
query
--null
Whether each format is terminated with \0 instead of newline. Expands to: --line_terminator_null=true
terminal output
query
--objc_debug_with_GLIBCXX=<true or false>
If set, and compilation mode is set to 'dbg', define GLIBCXX_DEBUG, GLIBCXX_DEBUG_PEDANTIC and GLIBCPP_CONCEPT_CHECKS.
--objc_enable_binary_stripping=<true or false>
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.
--objc_generate_linkmap=<true or false>
Specifies whether to generate a linkmap file.
--objc_header_scanner_tool=<build target label>
Location of tool to scan Objective-C code for inclusions and output a . headers_list file.
default: "@bazel_tools//tools/objc:header_scanner"
changes inputs
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--objc_header_thinning_partition_size=<integer>
The maximum number of source files to process within in each header scanning action.
default: "120"
host machine_resource_optimizations
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--objc_use_dotd_pruning=<true or false>
If set, .d files emitted by clang will be used to prune the set of inputs passed into objc compiles.
default: "true"
changes inputs
loading and_analysis
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--objccopt=<string>
Additional options to pass to Objective C compilation.
may be used multiple times
action command_lines
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--order_output=<no, deps, auto or full>
Output the results unordered (no), dependency-ordered (deps), or fully ordered (full). The default is 'auto', meaning that results are output either dependency-ordered or fully ordered, depending on the output formatter (dependency-ordered for proto, minrank, maxrank, and graph, fully ordered for all others). When output is fully ordered, nodes that would otherwise be unordered by the output formatter are alphabetized before output.
default: "auto"
terminal output
query
--order_results
Output the results in dependency-ordered (default) or unordered fashion. The unordered output is faster but only supported when --output is not minrank, maxrank, or graph. Expands to: --order_output=auto
terminal output
query
--output=<string>
The format in which the query results should be printed. Allowed values for query are: build, graph, label, label_kind, locations, maxrank, minrank, package, proto, xml.
default: "label"
terminal output
aquery
cquery
query
--output_base=<path>
If set, specifies the output location to which all build output will be written. Otherwise, the location will be ${OUTPUT_ROOT}/_blaze_${USER} /${MD5_OF_WORKSPACE_ROOT}. Note: If you specify a different option from one to the next Bazel invocation for this value, you'll likely start up a new, additional Bazel server. Bazel starts exactly one server per specified output base. Typically there is one output base per workspace - however, with this option you may have multiple output bases per workspace and thereby run multiple builds for the same client on the same machine concurrently. See 'bazel help shutdown' on how to shutdown a Bazel server.
default: see description
affects outputs
loses incremental_state
startup option
--output_filter=<valid Java regular expression>
Only shows warnings for rules with a name matching the provided regular expression.
--output_groups=<comma-separated list of options>
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.
may be used multiple times
execution
affects outputs
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--output_user_root=<path>
The user-specific directory beneath which all build outputs are written; by default, this is a function of $USER, but by specifying a constant, build outputs can be shared between collaborating users.
default: see description
affects outputs
loses incremental_state
startup option
--override_repository=<equals-separated mapping of repository name to path>
Overrides a repository with a local directory.
--package_path=<colon-separated list of options>
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'.
--packages=<true or false>
Dump package cache content.
default: "false"
bazel monitoring
dump
--parse_headers_verifies_modules=<true or false>
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.
default: "false"
loading and_analysis
changes inputs
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--per_file_copt=<comma-separated list of regex expressions with prefix '-' specifying excluded paths followed by an @ and a comma separated list of options>
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.
may be used multiple times
action command_lines
affects outputs
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--per_file_ltobackendopt=<comma-separated list of regex expressions with prefix '-' specifying excluded paths followed by an @ and a comma separated list of options>
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.
may be used multiple times
action command_lines
affects outputs
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--persistent_android_resource_processor
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
--platform_mappings=<relative path>
The location of a mapping file that describes which platform to use if none is set or which flags to set when a platform already exists. Must be relative to the main workspace root. Defaults to 'platform_mappings' (a file directly under the workspace root).
default: ""
affects outputs
changes inputs
loading and_analysis
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--platform_suffix=<string>
Specifies a suffix to be added to the configuration directory.
default: see description
loses incremental_state
affects outputs
loading and_analysis
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--platforms=<build target label>
The labels of the platform rules describing the target platforms for the current command.
default: ""
affects outputs
changes inputs
loading and_analysis
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--plugin=<build target label>
Plugins to use in the build. Currently works with java_plugin.
--print_action_mnemonics=<string>
Lists which mnemonics to filter print_action data by, no filtering takes place when left empty.
may be used multiple times
print_action
--print_relative_test_log_paths=<true or false>
If true, when printing the path to a test log, use relative path that makes use of the 'testlogs' convenience symlink. N.B. - A subsequent 'build'/'test'/etc invocation with a different configuration can cause the target of this symlink to change, making the path printed previously no longer useful.
default: "false"
affects outputs
coverage
test
--process_headers_in_dependencies=<true or false>
When building a target //a:a, process headers in all targets that //a:a depends on (if header processing is enabled for the toolchain).
--profile=<path>
If set, profile Bazel and write data to the specified file. Use bazel analyze-profile to analyze the profile.
--progress_in_terminal_title=<true or false>
Show the command progress in the terminal title. Useful to see what bazel is doing when having multiple terminal tabs.
--progress_report_interval=<integer in 0-3600 range>
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.
--proguard_top=<build target label>
Specifies which version of ProGuard to use for code removal when building a Java binary.
--project_id=<string>
Specifies the BES project identifier. Defaults to null.
--proto_compiler=<build target label>
The label of the proto-compiler.
default: "@com_google_protobuf//:protoc"
affects outputs
loading and_analysis
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--proto_toolchain_for_cc=<build target label>
Label of proto_lang_toolchain() which describes how to compile C++ protos
default: "@com_google_protobuf//:cc_toolchain"
affects outputs
loading and_analysis
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--proto_toolchain_for_j2objc=<build target label>
Label of proto_lang_toolchain() which describes how to compile j2objc protos
default: "@bazel_tools//tools/j2objc:j2objc_proto_toolchain"
affects outputs
loading and_analysis
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--proto_toolchain_for_java=<build target label>
Label of proto_lang_toolchain() which describes how to compile Java protos
default: "@com_google_protobuf//:java_toolchain"
affects outputs
loading and_analysis
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--proto_toolchain_for_javalite=<build target label>
Label of proto_lang_toolchain() which describes how to compile JavaLite protos
default: "@com_google_protobuf_javalite//:javalite_toolchain"
affects outputs
loading and_analysis
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--proto:default_values=<true or false>
If true, attributes whose value is not explicitly specified in the BUILD file are included; otherwise they are omitted. This option is applicable to --output=proto
default: "true"
terminal output
aquery
cquery
query
--proto:flatten_selects=<true or false>
If enabled, configurable attributes created by select() are flattened. For list types the flattened representation is a list containing each value of the select map exactly once. Scalar types are flattened to null.
default: "true"
build file_semantics
aquery
cquery
query
--proto:include_configurations=<true or false>
if enabled, proto output will include information about configurations. When disabled,cquery proto output format resembles query output format
default: "true"
affects outputs
cquery
--proto:output_rule_attrs=<comma-separated list of options>
Comma separated list of attributes to include in output. Defaults to all attributes. Set to empty string to not output any attribute. This option is applicable to --output=proto.
default: "all"
terminal output
aquery
cquery
query
--protocopt=<string>
Additional options to pass to the protobuf compiler.
--python_path=<string>
The absolute path of the Python interpreter invoked to run Python targets on the target platform. Deprecated; disabled by -- incompatible_use_python_toolchains.
default: see description
loading and_analysis
affects outputs
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--python_top=<build target label>
The label of a py_runtime representing the Python interpreter invoked to run Python targets on the target platform. Deprecated; disabled by -- incompatible_use_python_toolchains.
default: see description
loading and_analysis
affects outputs
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--python_version=<PY2 or PY3>
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.
default: see description
loading and_analysis
affects outputs
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--python2_path=<string>
Deprecated, no-op. Disabled by `--incompatible_use_python_toolchains`.
--python3_path=<string>
Deprecated, no-op. Disabled by `--incompatible_use_python_toolchains`.
--query_file=<string>
If set, query will read the query from the file named here, rather than on the command line. It is an error to specify a file here as well as a command-line query.
default: ""
changes inputs
query
--ram_utilization_factor=<integer>
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
--relative_locations=<true or false>
If true, the location of BUILD files in xml and proto outputs will be relative. By default, the location output is an absolute path and will not be consistent across machines. You can set this option to true to have a consistent result across machines.
default: "false"
terminal output
aquery
cquery
query
--remote_accept_cached=<true or false>
Whether to accept remotely cached action results.
--remote_allow_symlink_upload=<true or false>
If true, upload action symlink outputs to the remote cache. If this option is not enabled, cachable actions that output symlinks will fail.
--remote_cache=<string>
A URI of a caching endpoint. The supported schemas are http(s) and grpc. If no schema is provided we'll default to grpc. See https://docs.bazel.build/versions/master/remote-caching.html
--remote_cache_proxy=<string>
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.
--remote_default_platform_properties=<string>
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.
--remote_execution_priority=<integer>
The relative priority of actions to be executed remotely. The semantics of the particular priority values are server-dependent.
--remote_executor=<string>
HOST or HOST:PORT of a remote execution endpoint.
--remote_instance_name=<string>
Value to pass as instance_name in the remote execution API.
--remote_local_fallback=<true or false>
Whether to fall back to standalone local execution strategy if remote execution fails.
--remote_local_fallback_strategy=<string>
The strategy to use when remote execution has to fallback to local execution.
--remote_max_connections=<integer>
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.
default: "100"
host machine_resource_optimizations
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--remote_result_cache_priority=<integer>
The relative priority of remote actions to be stored in remote cache. The semantics of the particular priority values are server-dependent.
--remote_timeout=<integer>
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.
--remote_upload_local_results=<true or false>
Whether to upload locally executed action results to the remote cache.
--remote_verify_downloads=<true or false>
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.
--repository_cache=<path>
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.
--resource_autosense=<true or false>
This flag has no effect, and is deprecated
--rule_classes=<true or false>
Dump rule classes.
default: "false"
bazel monitoring
dump
--rules=<true or false>
Dump rules, including counts and memory usage (if memory is tracked).
default: "false"
bazel monitoring
dump
--run_under=<prefix in front of command>
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'
--runs_per_test=<positive integer or test_regex@runs. This flag may be passed more than once>
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.
--runs_per_test_detects_flakes=<true or false>
If true, any shard in which at least one run/attempt passes and at least one run/attempt fails gets a FLAKY status.
--sandbox_add_mount_pair=<single path or a 'source:target' pair>
Add additional path pair to mount in sandbox.
--sandbox_block_path=<string>
For sandboxed actions, disallow access to this path.
--sandbox_debug=<true or false>
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.
--sandbox_fake_hostname=<true or false>
Change the current hostname to 'localhost' for sandboxed actions.
--sandbox_fake_username=<true or false>
Change the current username to 'nobody' for sandboxed actions.
--sandbox_tmpfs_path=<string>
For sandboxed actions, mount an empty, writable directory at this path (if supported by the sandboxing implementation, ignored otherwise).
--sandbox_writable_path=<string>
For sandboxed actions, make an existing directory writable in the sandbox (if supported by the sandboxing implementation, ignored otherwise).
--save_temps=<true or false>
If set, temporary outputs from gcc will be saved. These include .s files (assembler code), .i files (preprocessed C) and .ii files (preprocessed C++).
--script_path=<path>
If set, write a shell script to the given file which invokes the target. If this option is set, the target is not run from bazel. Use 'bazel run --script_path=foo //foo && ./foo' to invoke target '//foo' This differs from 'bazel run //foo' in that the bazel lock is released and the executable is connected to the terminal's stdin.
default: see description
affects outputs
execution
run
--server_javabase=<string>
Path to the JVM used to execute Bazel itself.
default: ""
startup option
--server_jvm_out=<path>
The location to write the server's JVM's output. If unset then defaults to a location in output_base.
default: see description
affects outputs
loses incremental_state
startup option
--share_native_deps=<true or false>
If true, native libraries that contain identical functionality will be shared among different targets
default: "true"
loading and_analysis
affects outputs
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--shell_executable=<path>
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.
--short
Show only the names of the options, not their types or meanings. Expands to: --help_verbosity=short
affects outputs
terminal output
help
--show_loading_progress=<true or false>
If enabled, causes Bazel to print "Loading package:" messages.
--show_make_env=<true or false>
Include the "Make" environment in the output.
default: "false"
affects outputs
terminal output
info
--show_progress_rate_limit=<double>
Minimum number of seconds between progress messages in the output.
--show_result=<integer>
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.
--show_task_finish=<true or false>
Display progress messages when tasks complete, not just when they start.
--show_warnings=<true or false>
Output parser warnings to standard error (e.g. for conflicting flag options).
default: "false"
affects outputs
terminal output
canonicalize-flags
--shutdown_on_low_sys_mem=<true or false>
If max_idle_secs is set and the build server has been idle for a while, shut down the server when the system is low on free RAM. Linux only.
default: "false"
eagerness to_exit
loses incremental_state
startup option
--skyframe=<off, summary or detailed>
Dump Skyframe graph: 'off', 'summary', or 'detailed'.
default: "off"
bazel monitoring
dump
--skyframe_state=<true or false>
Without performing extra analysis, dump the current Action Graph from Skyframe. Note: Specifying a target with --skyframe_state is currently not supported. This flag is only available with --output=proto or -- output=textproto.
default: "false"
terminal output
aquery
--skylark_memory=<string>
Dumps a pprof-compatible memory profile to the specified path. To learn more please see <a href=https://github.com/google/pprof>pprof</a>.
default: see description
bazel monitoring
dump
--spawn_strategy=<comma-separated list of options>
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).
--split_apks=<true or false>
Whether to use split apks to install and update the application on the device. Works only with devices with Marshmallow or later
default: "false"
loading and_analysis
affects outputs
mobile-install
--stamp=<true or false>
Stamp binaries with the date, username, hostname, workspace information, etc.
--start=<no, cold, warm or debug>
How the app should be started after installing it. Set to WARM to preserve and restore application state on incremental installs.
default: "NO"
execution
mobile-install
--start_app
Whether to start the app after installing it. Expands to: --start=COLD
--strategy=<'name=value1[,..,valueN]' assignment>
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.
--strategy_regexp=<'<RegexFilter>=value[,value]' assignment>
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'.
--strict_filesets=<true or false>
If this option is enabled, filesets crossing package boundaries are reported as errors. It does not work when check_fileset_dependencies_recursively is disabled.
default: "false"
build file_semantics
eagerness to_exit
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--strict_proto_deps=<off, warn, error, strict or default>
Unless OFF, checks that a proto_library target explicitly declares all directly used targets as dependencies.
default: "error"
build file_semantics
eagerness to_exit
incompatible change
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--strict_system_includes=<true or false>
If true, headers found through system include paths (-isystem) are also required to be declared.
default: "false"
loading and_analysis
eagerness to_exit
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--strict_test_suite=<true or false>
If true, the tests() expression gives an error if it encounters a test_suite containing non-test targets.
default: "false"
build file_semantics
eagerness to_exit
query
--strip=<always, sometimes or never>
Specifies whether to strip binaries and shared libraries (using "-Wl,-- strip-debug"). The default value of 'sometimes' means strip iff -- compilation_mode=fastbuild.
--stripopt=<string>
Additional options to pass to strip when generating a '<name>.stripped' binary.
may be used multiple times
action command_lines
affects outputs
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--subcommands=<true, pretty_print or false>
Display the subcommands executed during a build.
--swiftcopt=<string>
Additional options to pass to Swift compilation.
may be used multiple times
action command_lines
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--symlink_prefix=<string>
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.
--system_rc=<true or false>
Whether or not to look for the system-wide bazelrc.
default: "true"
changes inputs
startup option
--target_environment=<build target label>
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.
--target_platform_fallback=<build target label>
The label of a platform rule that should be used if no target platform is set and no platform mapping matches the current set of flags.
default: "@bazel_tools//platforms:target_platform"
affects outputs
changes inputs
loading and_analysis
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--task_tree=<valid Java regular expression>
Print the tree of profiler tasks from all tasks matching the given regular expression.
default: see description
affects outputs
analyze-profile
--task_tree_threshold=<long integer>
When printing a task tree, will skip tasks with a duration that is less than the given threshold in milliseconds.
default: "50"
affects outputs
analyze-profile
--test_arg=<string>
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.
--test_env=<'name=value' assignment with an optional value part>
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.
--test_filter=<string>
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.
--test_keep_going=<true or false>
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.
--test_lang_filters=<comma-separated list of options>
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.
--test_output=<summary, errors, all or streamed>
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).
--test_result_expiration=<integer>
This option is deprecated and has no effect.
--test_sharding_strategy=<explicit or disabled>
Specify strategy for test sharding: 'explicit' to only use sharding if the 'shard_count' BUILD attribute is present. 'disabled' to never use test sharding.
--test_size_filters=<comma-separated list of values: small, medium, large or enormous>
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.
--test_strategy=<string>
Specifies which strategy to use when running tests.
--test_summary=<short, terse, detailed, none or testcase>
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.
--test_tag_filters=<comma-separated list of options>
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.
--test_timeout=<single integer or comma-separated list of 4 integers>
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.
--test_timeout_filters=<comma-separated list of values: short, moderate, long or eternal>
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.
--test_tmpdir=<path>
Specifies the base temporary directory for 'bazel test' to use.
--test_verbose_timeout_warnings=<true or false>
If true, print additional warnings when the actual test execution time does not match the timeout defined by the test (whether implied or explicit).
default: "false"
affects outputs
coverage
test
--tls_enabled=<true or false>
Specifies whether to use TLS for remote execution/caching and the build event service (BES).
--tool_tag=<string>
A tool name to attribute this Bazel invocation to.
--toolchain_resolution_debug=<true or false>
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.
--track_incremental_state=<true or false>
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.
--transitions=<full, lite or none>
The format in which cquery will print transition information.
default: "none"
affects outputs
cquery
--translations=<tri-state (auto, yes, no)>
Translate Java messages; bundle all translations into the jar for each affected rule.
--trim_test_configuration=<true or false>
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.
default: "false"
loading and_analysis
loses incremental_state
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--tvos_cpus=<comma-separated list of options>
Comma-separated list of architectures for which to build Apple tvOS binaries.
default: "x86_64"
loses incremental_state
loading and_analysis
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--tvos_minimum_os=<dotted version (for example '2.3' or '3.3alpha2.4')>
Minimum compatible tvOS version for target simulators and devices.
default: see description
loses incremental_state
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--tvos_sdk_version=<dotted version (for example '2.3' or '3.3alpha2.4')>
Specifies the version of the tvOS SDK to use to build tvOS applications.
default: see description
loses incremental_state
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--tvos_simulator_device=<string>
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.
--tvos_simulator_version=<dotted version (for example '2.3' or '3.3alpha2.4')>
The version of tvOS to run on the simulator when running or testing.
--ui=<true or false>
Switches to a progress bar that more explicitly shows progress, such as loaded packages and executed actions.
--ui_actions_shown=<integer>
Number of concurrent actions shown in the detailed progress bar; each action is shown on a separate line. The progress bar always shows at least one one, all numbers less than 1 are mapped to 1. This option has no effect if --noui is set.
--universe_scope=<comma-separated list of options>
A comma-separated set of target patterns (additive and subtractive). The query may be performed in the universe defined by the transitive closure of the specified targets. This option is used for the query and cquery commands. For cquery, the input to this option is the targets all answers are built under and so this option may affect configurations and transitions. If this option is not specified, the top-level targets are assumed to be the targets parsed from the query expression. Note: For cquery, not specifying this option may cause the build to break if targets parsed from the query expression are not buildable with top-level options.
default: ""
loading and_analysis
aquery
cquery
query
--unlimit_coredumps=<true or false>
Raises the soft coredump limit to the hard limit to make coredumps of the server (including the JVM) and the client possible under common conditions. Stick this flag in your bazelrc once and forget about it so that you get coredumps when you actually encounter a condition that triggers them.
default: "false"
bazel internal_configuration
startup option
--use_ijars=<true or false>
If enabled, this option causes Java compilation to use interface jars. This will result in faster incremental compilation, but error messages can be different.
--use_singlejar_apkbuilder=<true or false>
Build Android APKs with SingleJar.
--verbose_explanations=<true or false>
Increases the verbosity of the explanations issued if --explain is enabled. Has no effect if --explain is not enabled.
--verbose_failures=<true or false>
If a command fails, print out the full command line.
--verbose_test_summary=<true or false>
If true, print additional information (timing, number of failed runs, etc) in the test summary.
default: "true"
affects outputs
coverage
test
--vfs_stats=<true or false>
If present, include VFS path statistics.
default: "false"
affects outputs
analyze-profile
--vfs_stats_limit=<integer>
Maximum number of VFS path statistics to print.
default: "-1"
affects outputs
analyze-profile
--watchfs=<true or false>
If true, bazel tries to use the operating system's file watch service for local changes instead of scanning every file for a change.
default: "false"
deprecated
applies to all commands
--watchos_cpus=<comma-separated list of options>
Comma-separated list of architectures for which to build Apple watchOS binaries.
default: "i386"
loses incremental_state
loading and_analysis
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--watchos_minimum_os=<dotted version (for example '2.3' or '3.3alpha2.4')>
Minimum compatible watchOS version for target simulators and devices.
default: see description
loses incremental_state
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--watchos_sdk_version=<dotted version (for example '2.3' or '3.3alpha2.4')>
Specifies the version of the watchOS SDK to use to build watchOS applications.
default: see description
loses incremental_state
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--watchos_simulator_device=<string>
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.
--watchos_simulator_version=<dotted version (for example '2.3' or '3.3alpha2.4')>
The version of watchOS to run on the simulator when running or testing.
--worker_extra_flag=<'name=value' assignment>
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.
--worker_max_instances=<[name=]value, where value is an integer, or a keyword ("auto", "HOST_CPUS", "HOST_RAM"), optionally followed by an operation ([-|*]<float>) eg. "auto", "HOST_CPUS*.5">
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.
--worker_quit_after_build=<true or false>
If enabled, all workers quit after a build is done.
--worker_sandboxing=<true or false>
If enabled, workers will be executed in a sandboxed environment.
--worker_verbose=<true or false>
If enabled, prints verbose messages when workers are started, shutdown, ...
--workspace_rc=<true or false>
Whether or not to look for the workspace bazelrc file at $workspace/.bazelrc
default: "true"
changes inputs
startup option
--workspace_status_command=<path>
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.
--xbinary_fdo=<build target label>
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.
--xcode_version=<string>
If specified, uses Xcode of the given version for relevant build actions. If unspecified, uses the executor default version of Xcode.
default: see description
loses incremental_state
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--xcode_version_config=<build target label>
The label of the xcode_config rule to be used for selecting the Xcode version in the build configuration.
default: "@local_config_xcode//:host_xcodes"
loses incremental_state
loading and_analysis
aquery
build
clean
coverage
cquery
info
mobile-install
print_action
run
test
--xml:default_values=<true or false>
If true, rule attributes whose value is not explicitly specified in the BUILD file are printed; otherwise they are omitted.
default: "false"
terminal output
query
--xml:line_numbers=<true or false>
If true, XML output contains line numbers. Disabling this option may make diffs easier to read. This option is only applicable to --output=xml.
default: "true"
terminal output
query