Note the existence of a `execroot/` directory
To be true to the layout on disk, one should note the literal directory named `execroot` under the outputBase.
Also fix the indentation on `<workspace-name>/` due to the HTML escapes.
Closes
@@ -77,19 +77,26 @@ The directories are laid out as follows:
7ffd56a6e4cb724ea575aba15733d113/ <== Hash of the client's workspace directory (e.g.
/home/some-user/src/my-project): outputBase
action_cache/ <== Action cache directory hierarchy
- This contains the persistent record of the file metadata
- (timestamps, and perhaps eventually also MD5 sums) used by the
- FilesystemValueChecker.
+ This contains the persistent record of the file
+ metadata (timestamps, and perhaps eventually also MD5
+ sums) used by the FilesystemValueChecker.
action_outs/ <== Action output directory. This contains a file with the
- stdout/stderr for every action from the most recent bazel run
- that produced output.
- command.log <== A copy of the stdout/stderr output from the most recent bazel
- command.
- external/ <== The directory that remote repositories are downloaded/symlinked
- into.
- server/ <== The Bazel server puts all server-related files (such as socket
- file, logs, etc) here.
+ stdout/stderr for every action from the most recent
+ bazel run that produced output.
+ command.log <== A copy of the stdout/stderr output from the most
+ recent bazel command.
+ external/ <== The directory that remote repositories are
+ downloaded/symlinked into.
+ server/ <== The Bazel server puts all server-related files (such
+ as socket file, logs, etc) here.
jvm.out <== The debugging output for the server.
+ execroot/ <== The working directory for all actions. For special
+ cases such as sandboxing and remote execution, the
+ actions run in a directory that mimics execroot.
+ Implementation details, such as where the directories
+ are created, are intentionally hidden from the action.
+ All actions can access its inputs and outputs relative
+ to the execroot directory.
&lt;workspace-name&gt;/ <== Working tree for the Bazel build & root of symlink forest: execRoot
_bin/ <== Helper tools are linked from or copied to here.
@@ -122,7 +129,7 @@ The directories are laid out as follows:
&lt;packages&gt;/ <== Packages referenced in the build appear as if under a regular workspace
</pre>
-The layout of the *.runfiles directories is documented in more detail in the places pointed to by RunfilesSupport.
+The layout of the \*.runfiles directories is documented in more detail in the places pointed to by RunfilesSupport.
## `bazel clean`
