commit | a0af440205c46cdae2806a53266a9140a568a3a9 | [log] [tgz] |
---|---|---|
author | Luca Milanesio <luca.milanesio@gmail.com> | Wed Apr 16 01:01:51 2025 +0100 |
committer | Luca Milanesio <luca.milanesio@gmail.com> | Wed Apr 16 14:41:24 2025 +0100 |
tree | 685ebe365392881f94316ede0b333d070bdac172 | |
parent | aefeecc76848f6dce4cec4e775388b1315429e10 [diff] |
Verify that ref updates are not lost because of grace period Having a grace period for metrics updates should not impact the overall validity of the metrics but only affect how often they are updated. Add a new integration test that tries to add two branches in rapid sequence to a repository and assert that the result of number of loose refs should not change regardless of having a grace period configured or not. Bug: Issue 410584024 Change-Id: Iad865492f39dd5ca8746f89f16c0b7ebe21f60b6
This plugin allows a systematic collection of repository metrics. It‘s primary use-case is with Gerrit, however it’s possible for it to work with multiple Git SCM systems, including bare Git repositories.
Metrics are updated either upon a ref-update
receive or on a time based refresh interval. ref-update
events are received only on primary nodes, so on replicas gracePeriod
will need to be set.
Clone or link this plugin to the plugins directory of Gerrit‘s source tree, and then run bazel build on the plugin’s directory.
Example:
git clone --recursive https://gerrit.googlesource.com/gerrit git clone https://gerrit.googlesource.com/plugins/git-repo-metrics pushd gerrit/plugins && ln -s ../../git-repo-metrics . && popd cd gerrit && bazel build plugins/git-repo-metrics
The output plugin jar is created in:
bazel-genfiles/plugins/git-repo-metrics/git-repo-metrics.jar
Copy the git-repo-metrics.jar into the Gerrit's /plugins directory and wait for the plugin to be automatically loaded.
This plugin can also work with Git repositories hosted by other Git based SCM tools, however the metrics are still expose via Gerrit, so a dedicated Gerrit instance running alongside the current SCM tool is still required. So to make this plugin work with other Git SCM tools, a Gerrit installation needs to be set-up and the basePath
needs to be set to the git data directory of the tool of choice. You will also need to set gracePeriod
and forceCollection
, as when using a different SCM tool than Gerrit the usual hooks aren't triggered. Finally, a configuration option will need to be specified to indicate which Backend is being used. Currently supported backend, other than GERRIT are:
Find more in the configuration section below.
More information about the plugin configuration can be found in the config.md file.