| commit | 1e3e011b190e5d9cd4e292fa744fd4dc4196dac2 | [log] [tgz] |
|---|---|---|
| author | Antonio Barone <syntonyze@gmail.com> | Tue Jul 20 17:15:22 2021 +0200 |
| committer | Antonio Barone <syntonyze@gmail.com> | Mon Jul 26 11:12:17 2021 +0200 |
| tree | 4ab3707bc859e1e90c7f4f38463294326ff4a41e | |
| parent | 4894d3afdde0b0aab31ad8aaa720849c1ad569ce [diff] |
Consume scheduled replication events Prior to this change replication-status was only consuming completed replication events, that is, replication events that already completed, either successfully or not. Now, consume also scheduled replication events, so that when querying the REST-API it is possible to have visibility on replication events that are currently scheduled, but have yet to be completed. Bug: Issue 14802 Change-Id: I49fb3d5cf94732e5193529336fa224a87c561d63
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