| commit | ed12dcd69cf21fc3ee558a20939555156c90f39e | [log] [tgz] |
|---|---|---|
| author | Fabio Ponciroli <Ponch78@gmail.com> | Fri Apr 11 20:34:07 2025 +0200 |
| committer | Fabio Ponciroli <Ponch78@gmail.com> | Mon Apr 14 22:28:47 2025 +0200 |
| tree | cf152dca29f8864030675be1f29d590ede30b938 | |
| parent | ca31c4450f25d0656b3e1e465604c09d23240b51 [diff] |
Trigger collection on ref-replicated event replication-done events are only emitted when replication happens syncronously via fetch. We need to rely on ref-replicated events instead which are always emitted. Now, only ref-updated and *-ref-replicated events originating from the current node are processed. Such events in a multi primary setutp are forwarded by either multi-site or high-availability to the peer nodes. Change-Id: I28780cf0ce801a22e0ad7cb20a61c1000e3f1119
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.