commit	bf7c5de140a621ea99b4458d56e62af1f37cb93e	[log] [tgz]
author	Luca Milanesio <luca.milanesio@gmail.com>	Fri Oct 03 09:52:21 2025 -0700
committer	Luca Milanesio <luca.milanesio@gmail.com>	Fri Oct 03 09:53:22 2025 -0700
tree	b845e0c4f430733e6d3b16acecb75320838f7934
parent	8414f6b29d8282e056e4f40404c37b8be416a208 [diff]

tree: b845e0c4f430733e6d3b16acecb75320838f7934

README.md

DEPRECATION NOTICE

GerritForge has decided to change the license to BSL therefore the Apache 2.0 version of this plugin is deprecated. The recommended version of the replication-status plugin is on GitHub and the development continues on GerritHub.io

Replication-status (DEPRECATED)

Record and display the repository's replication status without having to dig into the Gerrit replication_log

Consumes replication events and updates a cache with the latest replication status of specific refs to specific remotes.

Dependencies

The @PLUGIN@ depends on the replication plugin. Check the configuration section for more details.

REST API

The cache information is then exposed via a project's resource REST endpoint:

curl -v --user <user> '<gerrit-server>/a/projects/<project-name>/remotes/<remote-url>/replication-status'

: an (url-encoded) project repository
: an (url-encoded) remote URL for the replication

For instance, to assess the replication status of the project some/project to the https://github.com/some/project.git URL, the following endpoint should be called:

curl -v --user <user> '<gerrit-server>/a/projects/some%2Fproject/remotes/https%3A%2F%2Fgithub.com%2Fsome%2Fproject.git/replication-status'

A payload, similar to this may be returned:

{
  "remotes": {
    "https://github.com/some/project.git": {
      "status": {
        "refs/changes/01/1/meta": {
          "type": "PUSH",
          "status": "SUCCEEDED",
          "when": 1626688830
        },
        "refs/changes/03/3/meta": {
          "type": "PUSH",
          "status": "SUCCEEDED",
          "when": 1626688854
        },
        "refs/changes/03/3/1": {
          "type": "PUSH",
          "status": "SUCCEEDED",
          "when": 1626688854
        },
        "refs/changes/02/2/1": {
          "type": "PUSH",
          "status": "SUCCEEDED",
          "when": 1626688844
        },
        "refs/changes/02/2/meta": {
          "type": "PUSH",
          "status": "SUCCEEDED",
          "when": 1626688844
        },
        "refs/changes/01/1/1": {
          "type": "PUSH",
          "status": "SUCCEEDED",
          "when": 1626688830
        },
        "refs/changes/04/4/meta": {
          "type": "PULL",
          "status": "SUCCEEDED",
          "when": 1628000641
        },
        "refs/changes/04/4/1": {
          "type": "PULL",
          "status": "SUCCEEDED",
          "when": 1628000641
        }
      }
    }
  },
  "status": "OK",
  "project": "some/project"
}

HTTP status

The endpoint returns different HTTP response code depending on the result:

200 OK - The endpoint was called successfully, and a payload returned
404 Not Found - Project was not found
500 Failure - An unexpected server error occurred
403 Forbidden - The user has no permission to query the endpoint. Only Administrators and project owners are allowed

Overall status

The REST-API response shows a status field, which shows the overall replication-status of the projects for the specified remote.

OK - all the refs have successfully replicated
FAILED - Some refs have not replicated successfully

TODO

Does not consume pull-replication events.