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_objc_provider_resources --
incompatible_disable_third_party_license_checking --
incompatible_disallow_dict_plus --incompatible_disallow_empty_glob --
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_rule_execution_platform_constraints_allowed --
incompatible_disallow_struct_provider_syntax --
incompatible_do_not_split_linking_cmdline --
incompatible_expand_directories --incompatible_new_actions_api --
incompatible_no_attr_license --incompatible_no_kwargs_in_build_files --
incompatible_no_output_attr_default --
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_static_name_resolution_in_build_files --
incompatible_string_join_requires_strings --
incompatible_tls_enabled_removed
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.
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.
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
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.
How often to perform a connectivity and reachability check for remote
services (eg. 5s). 0 disables the check and assumes connectivity.
Use terminal cursor controls to minimize scrolling output going to stderr.
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.
Additional places to search for archives before accessing the network to
download them.
If used, it is possible to define a mapping between external repositories
and some (mostly likely ignored by .bazelignore) directories. The
repository rule can read and update files in those directories, and the
changes will be visible in the same build. Use attribute
'managed_directories' of the global workspace() function in WORKSPACE file
to define the mapping.
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 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. 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.
--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, remote_cache_check, remote_download or unknown>
Specifies additional profile tasks to be included in the profile.
If set, Bazel will measure cpu usage and add it to the JSON profile.
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
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.
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.
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.
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().
Unused. Will be removed in future versions of Bazel.
If true, disables all license checking logic
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, 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, 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.
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.
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, *args and **kwargs are not allowed in BUILD files. See
https://github.com/bazelbuild/bazel/issues/8021
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 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, BUILD files use static name resolution (which can find
errors in code that is not executed). See https://github.
com/bazelbuild/bazel/issues/8022
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
If set to true, bazel will handle --tls_enabled as a not existing flag.See
#8061 for details.
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.
--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.
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.
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 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.
Minimum number of seconds between progress messages in the output.
Display progress messages when tasks complete, not just when they start.
DEPRECATED. Specifies whether to use TLS for remote execution/caching and the build event service (BES). See #8061 for details.
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.
Switches to a progress bar that more explicitly shows progress, such as loaded packages and executed actions.
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.