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_always_check_depset_elements -- incompatible_applicable_licenses -- incompatible_bzl_disallow_load_after_statement -- incompatible_depset_for_libraries_to_link_getter -- 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_empty_glob --incompatible_disallow_legacy_javainfo --incompatible_disallow_struct_provider_syntax -- incompatible_do_not_split_linking_cmdline -- incompatible_enable_profile_by_default --incompatible_new_actions_api -- incompatible_no_attr_license --incompatible_no_implicit_file_export -- incompatible_no_output_attr_default --incompatible_no_rule_outputs_param --incompatible_no_support_tools_in_action_inputs -- incompatible_no_target_output_group -- incompatible_remote_results_ignore_disk --incompatible_remote_symlinks -- incompatible_remove_binary_profile -- incompatible_remove_enabled_toolchain_types -- incompatible_require_linker_input_cc_api -- incompatible_restrict_named_params --incompatible_restrict_string_escapes --incompatible_run_shell_command_string -- incompatible_tls_enabled_removed -- incompatible_use_cc_configure_from_rules_cc -- incompatible_visibility_private_attributes_at_definition

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.The supported schemas are grpc and grpcs (grpc with TLS enabled). If no schema is provided bazel'll default to grpcs. Specify grpc:// schema to disable TLS.

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.

Connect to the Build Event Service through a proxy. Currently this flag can only be used to configure a Unix domain socket (unix:/path/to/socket).

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.

Enables an expensive additional check that causes depset construction to fail fast if the depset's depth would exceed the limit specified by `-- nested_set_depth_limit`. Ordinarily this failure occurs only when the depset is flattened, which may be far from its point of creation.

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.

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

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

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, freebsd, and openbsd. Enabling this flag is equivalent to using --config=linux on Linux, --config=windows on Windows, etc.

If set to true, Action objects support an `args` field: a frozen Args object which contains all action arguments.

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 enabled, adds the JSON profile path to the log.

If set to true, allows Starlark aspects to be defined with `apply_to_generating_rules`, which will enable them to propagate through output file target nodes.

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, rule attributes and Starlark API methods needed for the rule cc_shared_library will be available

If set to true, the auto-generated //external package will not be available anymore. Bazel will still be unable to parse the file 'external/BUILD', but globs reaching into external/ from the unnamed package will work.

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.

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.

Includes the extra "out" attribute in action events that contains the exec path to the action's primary output.

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

If set to true, enables Ninja execution functionality.

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.

A URI of a remote downloader endpoint. The supported schemas are grpc and grpcs (grpc with TLS enabled). If no schema is provided bazel will default to grpcs. Specify grpc:// schema to disable TLS.

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

If set to true, repository_rule gains some remote execution capabilities.

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

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

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

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

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

If set to true, non-main repositories are planted as symlinks to the main repository in the execution root. That is, all repositories are direct children of the $output_base/execution_root directory. This has the side effect of freeing up $output_base/execution_root/__main__/external for the real top-level 'external' directory.

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().

Stream log file uploads directly to the remote storage rather than writing them to disk.

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.

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.

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.

Scale all timeouts related to http downloads by the given factor

Check the validity of elements added to depsets, in all constructors. Elements must be immutable, but historically the depset(direct=...) constructor forgot to check. Use tuples instead of lists in depset elements. See https://github.com/bazelbuild/bazel/issues/10313 for details.

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 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, the default value of the `allow_empty` argument of glob() is False.

Deprecated. No-op.

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

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.

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, (used) source files are are package private unless exported explicitly. See https://github. com/bazelbuild/proposals/blob/master/designs/2019-10-24-file-visibility.md

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, --noremote_upload_local_results and -- noremote_accept_cached will not apply to the disk cache. If a combined cache is used: --noremote_upload_local_results will cause results to be written to the disk cache, but not uploaded to the remote cache. --noremote_accept_cached will result in Bazel checking for results in the disk cache, but not in the remote cache. See #8216 for details.

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

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

If set to true, the platform configuration fragment cannot access the (deprecated) list of enabled toolchain types.

If set to true, rule create_linking_context will require linker_inputs instead of libraries_to_link. The old getters of linking_context will also be disabled and just linker_inputs 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

No-op. See #8061 for details.

When true, Bazel will no longer allow using cc_configure from @bazel_tools. Please see https://github.com/bazelbuild/bazel/issues/10134 for details and migration instructions.

If set to true, the visibility of private rule attributes is checked with respect to the rule definition, rather than the rule usage.

If enabled, Bazel compresses the JSON-format profile with gzip. By default, this is decided based on the extension of the file specified in --profile.

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

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

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

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.

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.

Overrides a repository with a local directory.

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

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

Whether to accept remotely cached action results.

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

A URI of a caching endpoint. The supported schemas are http, https, grpc and grpcs (grpc with TLS enabled). If no schema is provided bazel will default to grpcs. Specify grpc:// or http:// schema to disable TLS.See https://docs.bazel.build/versions/master/remote-caching.html

Specify a header that will be included in cache requests: --remote_cache_header=Name=Value. Multiple headers can be passed by specifying the flag multiple times. Multiple values for the same name will be converted to a comma-separated list.

Set the default exec properties to be used as the remote execution platform if an execution platform does not already set exec_properties.

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.

Does not download any remote build outputs to the local machine. This flag is a shortcut for three flags: --experimental_inmemory_jdeps_files, -- experimental_inmemory_dotd_files and -- experimental_remote_download_outputs=minimal. Expands to: --nobuild_runfile_links --experimental_inmemory_jdeps_files -- experimental_inmemory_dotd_files -- experimental_remote_download_outputs=minimal

If set to 'minimal' doesn't download any remote build outputs to the local machine, except the ones required by local actions. If set to 'toplevel' behaves like'minimal' except that it also downloads outputs of top level targets to the local machine. Both options can significantly reduce build times if network bandwidth is a bottleneck.

Only downloads remote outputs of top level targets to the local machine. This flag is a shortcut for three flags: -- experimental_inmemory_jdeps_files, --experimental_inmemory_dotd_files and -- experimental_remote_download_outputs=toplevel. Expands to: --experimental_inmemory_jdeps_files -- experimental_inmemory_dotd_files -- experimental_remote_download_outputs=toplevel

Specify a header that will be included in remote downloader requests: --remote_downloader_header=Name=Value. Multiple headers can be passed by specifying the flag multiple times. Multiple values for the same name will be converted to a comma-separated list.

Specify a header that will be included in execution requests: --remote_exec_header=Name=Value. Multiple headers can be passed by specifying the flag multiple times. Multiple values for the same name will be converted to a comma-separated list.

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

HOST or HOST:PORT of a remote execution endpoint.The supported schemas are grpc and grpcs (grpc with TLS enabled). If no schema is provided bazel'll default to grpcs. Specify grpc:// schema to disable TLS.

Specify a header that will be included in requests: --remote_header=Name=Value. Multiple headers can be passed by specifying the flag multiple times. Multiple values for the same name will be converted to a comma-separated list.

Value to pass as instance_name in the remote execution API.

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

No-op, deprecated. See https://github.com/bazelbuild/bazel/issues/7480 for details.

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.

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

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

The maximum number of attempts to retry a transient error. If set to 0, retries are disabled.

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

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

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

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

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

Display progress messages during a build.

Minimum number of seconds between progress messages in the output.

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

Include timestamps in messages

Writes into the specified file a pprof profile of CPU usage by all Starlark threads.

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.