Include inputs and outputs actions in the action graph dump. This option
does only apply to --action_graph.
Include command line of actions in the action graph dump. This option does
only apply to --action_graph.
Comma separated list of targets to include in action graph dump. Defaults
to all attributes. This option does only apply to --action_graph.
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
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
If true, all rules and files under //third_party must declare licenses([])
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.
--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.
If set, Bazel will measure cpu usage and add it to the JSON profile.
If set to true, restricts a number of Starlark built-in function parameters
to be only specifiable positionally (and not by keyword).
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.
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.
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.
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, 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.
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, 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 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, java_common APIs that take a java_toolchain or
host_javabase parameter require a JavaTootoolchainInfo or JavaRuntimeInfo
instead of a configured target.
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.
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.
Minimum number of seconds between progress messages in the output.
Display progress messages when tasks complete, not just when they start.
Dumps a pprof-compatible memory profile to the specified path. To learn
more please see <a href=https://github.com/google/pprof>pprof</a>.
Specifies whether to use TLS for remote execution/caching and the build event service (BES).
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.