Split cache-chroniclemap ITs into a separate build targets

So that they can be executed in parallel boosting the overal testing
performance (especially on RBE) and one doesn't have to check log in
order to find which IT failed.

Change-Id: Id04afb5561aa50be5f3fed19a935e8bdc4ed9dd3
1 file changed
tree: 6e02969112eb74f9c71f8f1123b8871878205aad
  1. src/
  2. .gitignore
  3. BUILD
  4. external_plugin_deps.bzl
  5. Jenkinsfile
  7. README.md

Persistent cache for Gerrit, based on ChronicleMap

Non-blocking and super-fast on-disk cache libModule for Gerrit Code Review based on ChronicleMap on-disk implementation.

How to build

This libModule is built like a Gerrit in-tree plugin, using Bazelisk. See the build instructions for more details.


  • Install cache-chronicalmap module

Install the chronicle-map module into the $GERRIT_SITE/lib directory.

Add the cache-chroniclemap module to $GERRIT_SITE/etc/gerrit.config as follows:

  installModule = com.googlesource.gerrit.modules.cache.chroniclemap.ChronicleMapCacheModule

For further information and supported options, refer to config documentation.

Migration from H2 caches

You can check how to migrate from H2 to chronicle-map here.