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_tools_defaults_package --
incompatible_disallow_conflicting_providers --
incompatible_disallow_data_transition --incompatible_disallow_dict_plus --
incompatible_disallow_filetype --incompatible_disallow_legacy_javainfo --
incompatible_disallow_old_style_args_add --
incompatible_disallow_slash_operator --incompatible_expand_directories --
incompatible_generate_javacommon_source_jar --
incompatible_never_use_embedded_jdk_for_javabase --
incompatible_new_actions_api --
incompatible_no_support_tools_in_action_inputs --
incompatible_package_name_is_a_function --incompatible_range_type --
incompatible_remove_native_git_repository --
incompatible_remove_native_http_archive --
incompatible_static_name_resolution --incompatible_string_is_not_iterable
How to resolve aspect dependencies when the output format is one of {xml,
proto,record}. 'off' means no aspect dependencies are resolved,
'conservative' (the default) means all declared aspect dependencies are
added regardless of whether they are given the rule class of direct
dependencies, 'precise' means that only those aspects are added that are
possibly active given the rule class of the direct dependencies. Note that
precise mode requires loading other packages to evaluate a single target
thus making it slower than the other modes. Also note that even precise
mode is not completely precise: the decision whether to compute an aspect
is decided in the analysis phase, which is not run during 'bazel query'.
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.
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 and that the upload will continue in the background after a
build has finished.
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 the section does not exist, this flag is ignored. Note that it is currently only possible to provide these options on the command line, not in the rc files. The config sections and flag combinations they are equivalent to are located in the tools/*.blazerc config files.
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.
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.
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, 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, 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
Skylark respository rules that were executed.
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.
If list of repository rules for which the hash of the output directory
should be verified, provided a file is specified by --
experimental_respository_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.
The maximum number of condition labels to show. -1 means no truncation and
0 means no annotation. This option is only applicable to --output=graph.
If true, then the graph will be emitted 'factored', i.e. topologically-
equivalent nodes will be merged together and their labels concatenated.
This option is only applicable to --output=graph.
The maximum length of the label string for a graph node in the output.
Longer labels will be truncated; -1 means no truncation. This option is
only applicable to --output=graph.
Query: If disabled, dependencies on 'host configuration' targets will not
be included in the dependency graph over which the query operates. A 'host
configuration' dependency edge, such as the one from any 'proto_library'
rule to the Protocol Compiler, usually points to a tool executed during the
build (on the host machine) rather than a part of the same 'target'
program.
Cquery: If disabled, filters out all configured targets which cross a host
transition from the top-level target that discovered this configured
target. That means if the top-level target is in the target configuration,
only configured targets also in the target configuration will be returned.
If the top-level target is in the host configuration, only host configured
targets will be returned.
If enabled, implicit dependencies will be included in the dependency graph
over which the query operates. An implicit dependency is one that is not
explicitly specified in the BUILD file but added by bazel.
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 skylark attribute definition methods, such as attr.label().
If set to true, disallow use of deprecated resource fields on the Objc
provider.
If set to true, disallow rule implementation functions from returning
multiple instances of the same type of provider. (If false, only the last
in the list will be used.)
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, old-style JavaInfo provider construction is disallowed.
If set to true, vectorized calls to Args#add are disallowed.
If set to true, the `/` operator is disabled. Use `//` for integer division.
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, java_common.compile will always generate an output source
jar.
If set to true, the API to create actions is only available on `ctx.
actions`, not on `ctx`.
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, the values PACKAGE_NAME and REPOSITORY_NAME are not
available. Use the package_name() or repository_name() functions instead.
If set to true, range() will use the 'range' type instead of 'list'.
If set to true, the native git_repository rules are disabled; only the
skylark version will be available
If set to true, the native http_archive rules are disabled; only the
skylark version will be available
If set to true, the interpreter follows the semantics related to name
resolution, scoping, and shadowing, as defined in https://github.
com/bazelbuild/proposals/blob/master/docs/2018-06-18-name-resolution.md
If set to true, iterating over a string will throw an error. String
indexing and `len` are still allowed.
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.
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.
Output the results in dependency-ordered (default) or unordered fashion.
The unordered output is faster but only supported when --output is not
minrank, maxrank, or graph.
Expands to: --order_output=no
Whether each format is terminated with instead of newline.
Expands to: --line_terminator_null=true
Output the results unordered (no), dependency-ordered (deps), or fully
ordered (full). The default is 'auto', meaning that results are output
either dependency-ordered or fully ordered, depending on the output
formatter (dependency-ordered for proto, minrank, maxrank, and graph, fully
ordered for all others). When output is fully ordered, nodes that would
otherwise be unordered by the output formatter are alphabetized before
output.
Output the results in dependency-ordered (default) or unordered fashion.
The unordered output is faster but only supported when --output is not
minrank, maxrank, or graph.
Expands to: --order_output=auto
The format in which the query results should be printed. Allowed values for
query are: build, graph, label, label_kind, locations, maxrank, minrank,
package, proto, xml.
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.
If true, attributes whose value is not explicitly specified in the BUILD
file are included; otherwise they are omitted. This option is applicable to
--output=proto
If enabled, configurable attributes created by select() are flattened. For
list types the flattened representation is a list containing each value of
the select map exactly once. Scalar types are flattened to null.
Comma separated list of attributes to include in output. Defaults to all
attributes. Set to empty string to not output any attribute. This option is
applicable to --output=proto.
If set, query will read the query from the file named here, rather than on
the command line. It is an error to specify a file here as well as a
command-line query.
If true, the location of BUILD files in xml and proto outputs will be
relative. By default, the location output is an absolute path and will not
be consistent across machines. You can set this option to true to have a
consistent result across machines.
Specifies the cache location of the downloaded values obtained during the
fetching of external repositories.
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.
If true, the tests() expression gives an error if it encounters a
test_suite containing non-test targets.
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.
A comma-separated set of target patterns (additive and subtractive). The
query may be performed in the universe defined by the transitive closure of
the specified targets. This option is used for the query and cquery
commands.
For cquery, the input to this option is the targets all answers are built
under and so this option may affect configurations and transitions. If this
option is not specified, the top-level targets are assumed to be the
targets parsed from the query expression. Note: For cquery, not specifying
this option may cause the build to break if targets parsed from the query
expression are not buildable with top-level options.
If true, bazel tries to use the operating system's file watch service for local changes instead of scanning every file for a change.
If true, rule attributes whose value is not explicitly specified in the
BUILD file are printed; otherwise they are omitted.