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_for_libraries_to_link_getter -- incompatible_depset_is_not_iterable --incompatible_depset_union -- incompatible_disable_deprecated_attr_params -- incompatible_disable_depset_items -- incompatible_disable_target_provider_fields -- incompatible_disable_third_party_license_checking -- incompatible_disallow_dict_lookup_unhashable_keys -- incompatible_disallow_dict_plus --incompatible_disallow_empty_glob -- incompatible_disallow_hashing_frozen_mutables -- incompatible_disallow_legacy_javainfo -- incompatible_disallow_old_style_args_add -- incompatible_disallow_rule_execution_platform_constraints_allowed -- incompatible_disallow_struct_provider_syntax -- incompatible_disallow_unverified_http_downloads -- incompatible_do_not_split_linking_cmdline -- incompatible_enable_profile_by_default --incompatible_expand_directories --incompatible_new_actions_api --incompatible_no_attr_license -- incompatible_no_output_attr_default --incompatible_no_rule_outputs_param --incompatible_no_support_tools_in_action_inputs -- incompatible_no_target_output_group --incompatible_no_transitive_loads -- incompatible_objc_framework_cleanup --incompatible_remap_main_repo -- incompatible_remove_binary_profile --incompatible_remove_native_maven_jar --incompatible_restrict_named_params -- incompatible_restrict_string_escapes -- incompatible_run_shell_command_string -- incompatible_string_join_requires_strings -- incompatible_tls_enabled_removed

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.

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.

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

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

Custom key-value string pairs to supply in a build event.

Use terminal controls to colorize output.

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.

If true, Bazel picks up host-OS-specific config lines from bazelrc files. For example, if the host OS is Linux and you run bazel build, Bazel picks up lines starting with build:linux. Supported OS identifiers are linux, macos, windows, and freebsd. Enabling this flag is equivalent to using --config=linux on Linux, --config=windows on Windows, etc.

This flag will be removed in Bazel 1.0. Please do not use it. Incremental repository updates feature is now enabled without the flag.

If set to true, tags will be propagated from a target to the actions' execution requirements; otherwise tags are not propagated. See https: //github.com/bazelbuild/bazel/issues/8830 for details.

If true, expand Filesets in the BEP when presenting output files.

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.

If enabled, Bazel profiles the build and writes a JSON-format profile into a file in the output base. View profile by loading into chrome://tracing.

If set to true, exposes a number of experimental pieces of Starlark build API pertaining to Google legacy code.

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

Whether to always compute MD5 digests of files with multiple threads. Setting this to false may improve performance when using a spinning platter.

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 add action counts at the top of the JSON profile.

Specifies additional profile tasks to be included in the profile.

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

Slims down the size of the JSON profile by merging events if the profile gets too large.

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

If set to true, enables use of 'unused_inputs_list' in starlark action. run().

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

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.

Determines what kind of data is shown in the detailed progress bar. By default, it is set to show the oldest actions and their running time. The underlying data source is usually sampled in a mode-dependend way to fit within the number of lines given by --ui_actions_shown.

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

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.

Iff non-zero, then shutdown will only shut down the server if the total memory (in MB) consumed by the JVM exceeds this value.

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

When true, Bazel no longer returns a list from linking_context. libraries_to_link but returns a depset instead.

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, disable the 'items' parameter of the depset constructor. Use the 'transitive' and 'direct' parameters instead.

If set to true, disable the ability to access providers on 'target' objects via field syntax. Use provider-key syntax instead. For example, instead of using `ctx.attr.dep.my_info` to access `my_info` from inside a rule implementation function, use `ctx.attr.dep[MyInfo]`. See https://github. com/bazelbuild/bazel/issues/9014 for details.

If true, disables all license checking logic

If set to true, dict key lookups using `in` or `dict.get` will fail with unhashable types.

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

If set to true, the default value of the `allow_empty` argument of glob() is False.

If set to true, freezing a mutable object will not make it hashable.

Deprecated. No-op.

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

If set to true, disallow the use of the execution_platform_constraints_allowed attribute on rule().

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

If set, disallow downloads via plain http if no checksum is given

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.

If enabled, Bazel will generate a JSON profile by default.

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, disables the `outputs` parameter of the `rule()` Starlark function.

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 enabled, use the post-cleanup mode for prebuilt frameworks. The cleanup changes the objc provider API pertaining to frameworks. This change is expected to be transparent to most users unless they write their own Starlark rules to handle frameworks. See https://github. com/bazelbuild/bazel/issues/7944 for details.

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

If enabled, Bazel will write JSON-format profiles instead of binary profiles.

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

If set to true, restricts a number of Starlark built-in function parameters to be only specifiable positionally (and not by keyword).

If set to true, unknown string escapes like `\a` become rejected.

If set to true, the command parameter of actions.run_shell will only accept string

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

No-op. See #8061 for details.

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.

Limit on the depth of NestedSet, which is the internal data structure used to implement `depset` in Starlark. If a depset is flattened during evaluation of Starlark code or a NestedSet is flattened internally, and that data structure has a depth exceeding this limit, then the Bazel invocation will fail.

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

Specify the TLS client certificate to use.

No-op. See #8061 for details.

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.

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.

On Linux/macOS: If true, bazel tries to use the operating system's file watch service for local changes instead of scanning every file for a change. On Windows: this flag is a non-op.