opendev/gerrit
Code Issues Proposed changes

Remove documentation about cleaning the build cache

Browse Source 
The buck-cache folder is not used since change Ia9c58bc5a, and the whole
process of cleaning the build cache is different with bazel anyway.

Rather than attempting to document this for bazel, where we rarely need
to wipe the build cache (compared to with buck), just remove that part of
the documentation.

Change-Id: I1ae4e89f1b9c9a8cc3ce75a18a6e48db2d1b2ba2
This commit is contained in:
David Pursehouse 2018-04-26 13:16:21 +09:00
parent 5dd0174832
commit 89050c03bc
1 changed files with 0 additions and 20 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
Documentation/dev-bazel.txt
View File

@ -358,26 +358,6 @@ To consume the JGit dependency from the development tree, edit
`lib/jgit/jgit.bzl` setting LOCAL_JGIT_REPO to a directory holding a `lib/jgit/jgit.bzl` setting LOCAL_JGIT_REPO to a directory holding a
JGit repository. JGit repository.
[[clean-cache]]
=== Cleaning The download cache
The cache for the Gerrit Code Review project is located in
`~/.gerritcodereview/buck-cache/locally-built-artifacts`.
If you really do need to clean the cache manually, then:
----
rm -rf ~/.gerritcodereview/buck-cache/locally-built-artifacts
----
Note that the root `buck-cache` folder should not be deleted as it also contains
the `downloaded-artifacts` directory, which holds the artifacts that got
downloaded (not built locally).
[NOTE] When building with Bazel the artifacts are still cached in
`~/.gerritcodereview/buck-cache/`. This allows Bazel to make use of
libraries that were previously downloaded by Buck.
GERRIT GERRIT
------ ------
Part of link:index.html[Gerrit Code Review] Part of link:index.html[Gerrit Code Review]