opendev/gerrit
Code Issues Proposed changes

dev-bazel: Improve documentation of build caches

Browse Source 
Change-Id: Id447987afcacbc242924215e187ff39e4912d915
This commit is contained in:
David Pursehouse
2018-06-05 14:49:06 +09:00
parent cb13335e63
commit 42cb2931be
1 changed files with 15 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
Documentation/dev-bazel.txt
View File

@@ -366,15 +366,26 @@ JGit repository.
[[bazel-local-caches]]
To accelerate builds, number of caches are activated per default:
To accelerate builds, several caches are activated per default:
* ~/.gerritcodereview/bazel-cache/downloaded-artifacts
* ~/.gerritcodereview/bazel-cache/repository
* ~/.gerritcodereview/bazel-cache/cas
All these caches currently don't have max. size limit,
link:https://github.com/bazelbuild/bazel/issues/5139[see this pending issue],
The users should watch their size and clean them manually if needed.
Currently none of these caches have a maximum size limit. See
link:https://github.com/bazelbuild/bazel/issues/5139[this bazel issue] for
details. Users should watch the cache sizes and clean them manually if
necessary.
Due to the `--experimental_strict_action_env` option used in `bazelrc`
it is possible that some commands required by the build are not found
on the PATH, causing the build to fail. In this case the PATH used in
the build can be overridden with the `--action_env=PATH` directive in
the user's `~/.bazelrc` file, for example:
----
build --action_env=PATH=/usr/local/opt/coreutils/libexec/gnubin/:/usr/local/bin/:/usr/bin/
----
GERRIT
------