e72efb1338
While we removed support for magic `refs/publish/...` branches some time ago, there are still lots of git-review users in the wild that use an old git-review that relies on `refs/publish/...` (i.e.: git-review before 1.27). Their git-review fails with error messages like: remote: error: branch refs/publish/master: remote: use a SHA1 visible to you, or get update permission on the ref remote: User: <redacted> remote: Contact an administrator to fix the permissions and remote: error: branch refs/publish/master: remote: You need 'Create' rights to create new references. remote: User: <redacted> remote: Contact an administrator to fix the permissions which are of little use for them. Since old git-review versions are still so popular with users, we add a hint towards upgrading their git-review, upon errors on `refs/publish/...`. So error messages for users of a too old git-review now look like remote: error: branch refs/publish/master: remote: If you are using git-review, update to at least git-review 1.27. Otherwise: remote: use a SHA1 visible to you, or get update permission on the ref remote: User: <redacted> remote: Contact an administrator to fix the permissions To see how popular old git-review versions still are with users, consider Wikimedia's Gerrit upgrade. They had a few bugs reports about this issue, a few more pastebins, where users complained, and at least a dozen of cases where people complained in IRC. All within first five days after migration. Co-Author: Kunal Mehta <legoktm@member.fsf.org> Change-Id: Ia121a90f229e4044b2514132346719fcb8096e9c
Gerrit Code Review
Gerrit is a code review and project management tool for Git based projects.
Objective
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.
Documentation
For information about how to install and use Gerrit, refer to the documentation.
Source
Our canonical Git repository is located on googlesource.com. There is a mirror of the repository on Github.
Reporting bugs
Please report bugs on the issue tracker.
Contribute
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.
Getting in contact
The Developer Mailing list is repo-discuss on Google Groups.
License
Gerrit is provided under the Apache License 2.0.
Build
Install Bazel and run the following:
git clone --recurse-submodules https://gerrit.googlesource.com/gerrit
cd gerrit && bazel build release
Install binary packages (Deb/Rpm)
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>]
Use pre-built Gerrit images on Docker
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.