| commit | 3da03680cba4703803a0a8a2b2fd6c8900d7fd24 | [log] [tgz] |
|---|---|---|
| author | Daniele Sassoli <danielesassoli@gmail.com> | Sun Mar 09 22:05:25 2025 +0000 |
| committer | Daniele Sassoli <danielesassoli@gmail.com> | Mon Mar 10 00:33:57 2025 -0800 |
| tree | 36b3525e80d071abeb6e753a1ce74a6782a31e80 | |
| parent | 17352078b2afdc1b3fde40d59a940c3a3ca32b5d [diff] |
repoPath for GitLab should not add git extension Gerrit already adds .git extension to the project name when searching for a project on disk. Change-Id: I3b61975b59da2385a79a1e4f5a890e10108a6006
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.