info command prints values for the following keys.
A key can be supplied as an argument, such as
info bazel-bin or if no argument
is given, most key/values are printed.
|Configuration dependent directory for binaries.
|Configuration dependent directory for generated files.
|Configuration dependent directory for logs from a test run.
|Print a binary-encoded protocol buffer with the build language structure.
|Information about the character encoding used by the running JVM.
|The specifications to freeze the current client environment. 1
|Location of the log containing the output from the build commands.
|Amount of memory in bytes that is committed for the JVM to use.
|The default package path.
|A directory that makes all input and output files visible to the build.
|Number of garbage collection runs.
|The approximate accumulated time spend on garbage collection.
|The installation base directory.
|Location of the current Java runtime.
|Name and version of the current Java runtime environment.
|Name and version of the current Java virtual machine.
|Maximum amount of memory in bytes that can be used for memory management.
|A directory for shared bazel state. 2
|The output directory.
|The search path for resolving package labels.
|The peak amount of used memory in bytes after any call to System.gc().
|bazel release identifier.
|The location of the repository download cache used.
|The bazel server log path.
|The bazel process id.
|The effective set of Starlark semantics option values.
|The amount of used memory in bytes. 3
|The amount of used memory in bytes after a call to System.gc().
|The working directory of the server.
- Note that this is not a good indicator of the actual memory use, as it includes any remaining inaccessible memory.↩
- As well as tool and strategy specific subdirectories.↩
- The output can be added to the project-specific rc file. See https://bazel.build/designs/2016/06/21/environment.html↩