tree ad9d366913d064482784af32c31f08db43432577
parent ea284be0932b318dc59d6b6b3522d935731be89d
author Luca Milanesio <luca.milanesio@gmail.com> 1585778013 +0100
committer Luca Milanesio <luca.milanesio@gmail.com> 1586165770 +0000

Use remote Bazel cache on https://gerrit-ci.gerritforge.com/cache

Use Bazel cache across different worker nodes: by using the same
global Bazel cache allow reusing artifacts from the previous builds
and avoid running tests if the dependent code hasn't changed.

Using remote Bazel cache also avoids re-building if nothing changed,
as the build artifacts would be fetched from the remote Bazel cache
thanks to cache hits.

In fact, the 'bazel build :release :api' would be a no-op if only
some files were changed that do not contribute to the final artifact
(say contrib directory).

How to test the Bazel cache locally:

$ bazelisk build \
  --remote_cache=https://gerrit-ci.gerritforge.com/cache \
  --noremote_upload_local_results \
  gerrit

Change-Id: I261d086bb5082969f422ff8a79ce6ec3fed7eb9a