Documentation: Recommend Bazelisk to launch bazel
Change-Id: Ic9dfd80fe7eadd1c52f3c0cac0d78e61654dd34c
diff --git a/Documentation/dev-bazel.txt b/Documentation/dev-bazel.txt
index b62a0a4d6..9d1f6a9 100644
--- a/Documentation/dev-bazel.txt
+++ b/Documentation/dev-bazel.txt
@@ -9,12 +9,22 @@
* A JDK for Java 8|9|10|11|...
* Python 2 or 3
* Node.js
-* link:https://www.bazel.io/versions/master/docs/install.html[Bazel] directly
-or through link:https://github.com/bazelbuild/bazelisk[Bazelisk]
+* link:https://bazel.build/[Bazel] -launched with
+link:https://github.com/bazelbuild/bazelisk[Bazelisk]
* Maven
* zip, unzip
* gcc
+[[bazel]]
+=== Bazel
+
+link:https://github.com/bazelbuild/bazelisk[Bazelisk] includes a
+link:https://bazel.build/[Bazel] version check and downloads the correct
+`bazel` version for the git project/repository. Bazelisk is the recommended
+`bazel` launcher for Gerrit. Once Bazelisk is installed locally, a `bazel`
+symlink can be created towards it. This is so that every `bazel` command
+seamlessly uses Bazelisk, which then runs the proper `bazel` binary version.
+
[[java]]
=== Java
diff --git a/Documentation/dev-readme.txt b/Documentation/dev-readme.txt
index 92d080b..fa0c184 100644
--- a/Documentation/dev-readme.txt
+++ b/Documentation/dev-readme.txt
@@ -1,7 +1,7 @@
= Gerrit Code Review: Developer Setup
To build a developer instance, you'll need link:https://bazel.build/[Bazel] to
-compile the code.
+compile the code, preferably launched with link:https://github.com/bazelbuild/bazelisk[Bazelisk].
== Getting the Source
