| commit | 5ab2f8b5d44c667ce93466c00c36aa13e8dba291 | [log] [tgz] |
|---|---|---|
| author | Luca Milanesio <luca.milanesio@gmail.com> | Wed Apr 30 18:40:40 2025 +0100 |
| committer | Luca Milanesio <luca.milanesio@gmail.com> | Wed Apr 30 13:23:37 2025 -0700 |
| tree | b1031a6d04bc7268b6c54d36396e033ab819113a | |
| parent | 4473b116b54844df0aab39e0df0849883312f90d [diff] |
Fix FakeMetricMaker metrics creation Following the introduction of the parametric metric based on the project name, the FakeMetricMaker was not amended accordingly causing the creation of incorrect runtime behaviour. As soon as the FakeMetricMaker start simulating the correct logic behind the metric generation, the test shouldRegisterMetricsOnlyOnce() starts failing which is a good thing: the code in GitRepoMetricsCache was broken in the detection of existing metrics therefore this failure is expected. Change-Id: I689f2bf2c2e9d39fc816ca2838cd4e594782ae3f
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.