If set, Bazel will be run as just a client process without a server,
instead of in the standard client/server mode. This is deprecated and will
be removed, please prefer shutting down the server explicitly if you wish
to avoid lingering servers.
Only on Linux; use 'batch' CPU scheduling for Blaze. This policy is useful
for workloads that are non-interactive, but do not want to lower their nice
value. See 'man 2 sched_setscheduler'. If false, then Bazel does not
perform a system call.
The location of the user .bazelrc file containing default values of Bazel
options. If unspecified, Bazel uses the first .bazelrc file it finds in the
following two locations: the workspace directory, then the user's home
directory. Use /dev/null to disable the search for a user rc file, e.g. in
release builds.
When --noblock_for_lock is passed, Bazel does not wait for a running
command to complete, but instead exits immediately.
If true, log debug information from the client to stderr. Changing this
option will not cause the server to restart.
The amount of time the client waits for each attempt to connect to the
server
If set, the execution root will be under $OUTPUT_BASE/execroot instead of
$OUTPUT_BASE.
Changed the expansion of --config flags to be done in-place, as opposed to
in a fixed point expansion between normal rc options and command-line
specified options.
If set, attempt to detect Java heap OOM conditions and exit before
thrashing. Only honored when --batch is also passed. In some cases, builds
that previously succeeded may OOM if they were close to OOMing before.
Deprecated: Use the command argument --
experimental_oom_more_eagerly_threshold instead.
If this flag is set, Bazel will OOM if, after two full GC's, more than this
percentage of the (old gen) heap is still occupied. Deprecated: Use the
command argument --experimental_oom_more_eagerly_threshold instead.
Convenience option to add some additional JVM startup flags, which cause the JVM to wait during startup until you connect from a JDWP-compliant debugger (like Eclipse) to port 5005. Expands to: --host_jvm_args=-Xdebug --host_jvm_args=-Xrunjdwp: transport=dt_socket,server=y,address=5005
Convenience option to add some profiler/debugger-specific JVM startup flags. Bazel has a list of known values that it maps to hard-coded JVM startup flags, possibly searching some hardcoded paths for certain files.
Disables all rc files, regardless of the values of other rc-modifying
flags, even if these flags come later in the list of startup options.
On Linux/macOS/non-Windows: no-op. On Windows: if true, then subprocess
arguments are escaped Windows-style. When false, the arguments are escaped
Bash-style. The Bash-style is buggy, the Windows-style is correct. See
https://github.com/bazelbuild/bazel/issues/7122
Only on Linux; set a level from 0-7 for best-effort IO scheduling using the
sys_ioprio_set system call. 0 is highest priority, 7 is lowest. The
anticipatory scheduler may only honor up to priority 4. If set to a
negative value, then Bazel does not perform a system call.
Sets the QoS service class of the bazel server when running on macOS.
This flag has no effect on all other platforms but is supported to ensure
rc files can be shared among them without changes. Possible values are:
user-interactive, user-initiated, default, utility, and background.
The number of seconds the build server will wait idling before shutting
down. Zero means that the server will never shutdown.
If set, specifies the output location to which all build output will be
written. Otherwise, the location will be ${OUTPUT_ROOT}/_blaze_${USER}
/${MD5_OF_WORKSPACE_ROOT}. Note: If you specify a different option from one
to the next Bazel invocation for this value, you'll likely start up a new,
additional Bazel server. Bazel starts exactly one server per specified
output base. Typically there is one output base per workspace - however,
with this option you may have multiple output bases per workspace and
thereby run multiple builds for the same client on the same machine
concurrently. See 'bazel help shutdown' on how to shutdown a Bazel server.
The user-specific directory beneath which all build outputs are written; by
default, this is a function of $USER, but by specifying a constant, build
outputs can be shared between collaborating users.
The location to write the server's JVM's output. If unset then defaults to
a location in output_base.
If max_idle_secs is set and the build server has been idle for a while,
shut down the server when the system is low on free RAM. Linux only.
Raises the soft coredump limit to the hard limit to make coredumps of the
server (including the JVM) and the client possible under common conditions.
Stick this flag in your bazelrc once and forget about it so that you get
coredumps when you actually encounter a condition that triggers them.
If true, bazel tries to use the operating system's file watch service
for local changes instead of scanning every file for a change.