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_data_transition --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_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_require_feature_configuration_for_pic -- incompatible_strict_argument_ordering -- incompatible_use_toolchain_providers_in_java_common

Whether to announce rc options.

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.

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

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

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

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

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

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

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

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

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

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

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

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

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

Whether all actions should be published.

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

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

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'.

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

Use terminal controls to colorize output going to stderr.

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.

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

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

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

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

Use external repositories for improved stability and speed when available.

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

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

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

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

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

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

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

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

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

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

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

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

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

The command for which the options should be canonicalized.

Forces --experimental_external_repositories.

A comma-separated list of Google Cloud authentication scopes.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.

Applies an invocation policy to the options to be canonicalized.

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.

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

The logging level.

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.

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

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

Specifies the BES project identifier. Defaults to null.

Display progress messages during a build.

Minimum number of seconds between progress messages in the output.

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

Include timestamps in messages

Output parser warnings to standard error (e.g. for conflicting flag options).

Specify the TLS client certificate to use.

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

A tool name to attribute this Bazel invocation to.

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.

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