commit | 1ee36f783f7d2d0c90aeb7b1f9e932031e0a5151 | [log] [tgz] |
---|---|---|
author | Fabio Ponciroli <ponch78@gmail.com> | Tue Nov 08 10:20:01 2022 +0000 |
committer | Fabio Ponciroli <ponch78@gmail.com> | Mon Nov 14 16:14:12 2022 +0100 |
tree | a89c627eb302c2ff24eedeef5d828b0d52820578 | |
parent | 7467a9323003f97672d89a7c094db3798580bd10 [diff] |
Missing "events" namespace in IT tests IT tests weren't adjusted in 7467a9323003f97672d89a7c094db3798580bd10 Also `targetNode` was deprecated, hence the use of `targetUri` instead. Change-Id: I137a6cb01923a35302faf81c1b38e8da5870281a
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.
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'
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": { "status": "SUCCEEDED", "when": 1626688830 }, "refs/changes/03/3/meta": { "status": "SUCCEEDED", "when": 1626688854 }, "refs/changes/03/3/1": { "status": "SUCCEEDED", "when": 1626688854 }, "refs/changes/02/2/1": { "status": "SUCCEEDED", "when": 1626688844 }, "refs/changes/02/2/meta": { "status": "SUCCEEDED", "when": 1626688844 }, "refs/changes/01/1/1": { "status": "SUCCEEDED", "when": 1626688830 } } } }, "status": "OK", "project": "some/project" }
The endpoint returns different HTTP response code depending on the result:
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 replicatedFAILED
- Some refs have not replicated successfully