commit | 9a5cc0ff9c7dd7cc9c6f13e5cd5b944a8aeaed6a | [log] [tgz] |
---|---|---|
author | Saša Živkov <sasa.zivkov@sap.com> | Thu Aug 01 04:24:23 2019 +0200 |
committer | Gerrit Code Review <noreply-gerritcodereview@google.com> | Thu Aug 01 02:24:23 2019 +0000 |
tree | 740461a550dc0f238b79c847a89c6fba08651a3b | |
parent | 3794f8f2a6b845a401c4a61b87a8df3da613ef12 [diff] |
Update git submodules * Update plugins/replication from branch 'stable-2.16' to aba8c72aaf29d0ece59779dc59e4ed6e97c401a0 - Consistently handle remote repository creation failures Failure to create remote repository was handled inconsistently in the three existing AdminApi implementations. This issue was present in the code even before the refactoring done in Ie760bf3e143b1d143b6e81ac6cfa816ef1f8d016. For example, creation of remote repository over SSH [1] didn't return a status back to the caller, while the Gerrit+SSH implementation [2] did return a boolean flag which was afterwards ignored by the caller [3]. Not handling remote repository creation failures had an ugly effect: we log the "Missing repository created; ..." [4], even if the repository creation failed. Let all three implementations of the AdminApi return a flag indicating the success/failure and make sure to handle it properly. Further, remove some redundant and potentially confusing parts of the log messages as they assume that failure to create missing repository can only be caused by using wrong protocol. [1] https://gerrit.googlesource.com/plugins/replication/+/d557ccc642c59a55750f560ce0d98870e1550d65/src/main/java/com/googlesource/gerrit/plugins/replication/ReplicationQueue.java#290 [2] https://gerrit.googlesource.com/plugins/replication/+/d557ccc642c59a55750f560ce0d98870e1550d65/src/main/java/com/googlesource/gerrit/plugins/replication/GerritSshApi.java#43 [3] https://gerrit.googlesource.com/plugins/replication/+/d557ccc642c59a55750f560ce0d98870e1550d65/src/main/java/com/googlesource/gerrit/plugins/replication/ReplicationQueue.java#259 [4] https://gerrit.googlesource.com/plugins/replication/+/092792edacf9c29732a560a30967b92664cd65f9/src/main/java/com/googlesource/gerrit/plugins/replication/PushOne.java#400 Change-Id: I6566f867138ab73c81ff7a67630772c3734e501b (cherry picked from commit b95d921d6db891dc724f619d957ab35e634f7e44)
Gerrit is a code review and project management tool for Git based projects.
Gerrit makes reviews easier by showing changes in a side-by-side display, and allowing inline comments to be added by any reviewer.
Gerrit simplifies Git based project maintainership by permitting any authorized user to submit changes to the master Git repository, rather than requiring all approved changes to be merged in by hand by the project maintainer.
For information about how to install and use Gerrit, refer to the documentation.
Our canonical Git repository is located on googlesource.com. There is a mirror of the repository on Github.
Please report bugs on the issue tracker.
Gerrit is the work of hundreds of contributors. We appreciate your help!
Please read the contribution guidelines.
Note that we do not accept Pull Requests via the Github mirror.
The Developer Mailing list is repo-discuss on Google Groups.
Gerrit is provided under the Apache License 2.0.
Install Bazel and run the following:
git clone --recurse-submodules https://gerrit.googlesource.com/gerrit cd gerrit && bazel build release
The instruction how to configure GerritForge/BinTray repositories is here
On Debian/Ubuntu run:
apt-get update & apt-get install gerrit=<version>-<release>
NOTE: release is a counter that starts with 1 and indicates the number of packages that have been released with the same version of the software.
On CentOS/RedHat run:
yum clean all && yum install gerrit-<version>[-<release>]
On Fedora run:
dnf clean all && dnf install gerrit-<version>[-<release>]
Docker images of Gerrit are available on DockerHub
To run a CentOS 7 based Gerrit image:
docker run -p 8080:8080 gerritforge/gerrit-centos7[:version]
To run a Ubuntu 15.04 based Gerrit image:
docker run -p 8080:8080 gerritforge/gerrit-ubuntu15.04[:version]
NOTE: release is optional. Last released package of the version is installed if the release number is omitted.