[ANNOUNCE] Gerrit 2.13.1

201 views
Skip to first unread message

Hugo Arès

unread,
Sep 23, 2016, 11:17:45 AM9/23/16
to Repo and Gerrit Discussion
Gerrit version 2.13.1 is now available.

Release notes:
http://gerrit-documentation.storage.googleapis.com/ReleaseNotes/ReleaseNotes-2.13.1.html

Documentation:
http://gerrit-documentation.storage.googleapis.com/Documentation/2.13.1/index.html

Log of changes since 2.13:
https://gerrit.googlesource.com/gerrit/+log/v2.13..v2.13.1

Download:
https://gerrit-releases.storage.googleapis.com/gerrit-2.13.1.war

SHA1:
1db213eb013c6555e582876ebd3d845066f1ef66

SHA256:
4b4fdb8e784b1ef93375a6cf9d1a1417e6c68aef7a2b6b0e4d885b472c9a3e0b

MD5:
c9dc5f23767c777a0d6c19bbb614541a

lucamilanesio

unread,
Sep 24, 2016, 8:10:38 PM9/24/16
to Repo and Gerrit Discussion
Binary packages (Deb / Rpm) of Gerrit version 2.13 are now available

If you have already installed Gerrit 2.10 / 2.11 / 2.12 using them, you need to execute:

Binary packages (Deb / Rpm).

(on Debian / Ubuntu)
apt-get update & apt-get install gerrit

(on CentOS / RedHat)
yum clean all && yum install gerrit

(on Fedora)
To install the GerritForge Yum repository, you need to execute only the first time:

and then to install Gerrit:
dnf clean all && dnf install gerrit

Docker images of Gerrit are available on DockerHub at:

In order to fetch Gerrit with CentOS 7:
docker pull gerritforge/gerrit-centos7

In order to fetch Gerrit with Ubuntu 15.04:
docker pull gerritforge/gerrit-ubuntu15.04

If you have not configured yet the GerritForge / BinTray repositories, the instructions are on:

David Ostrovsky

unread,
Sep 28, 2016, 10:06:41 AM9/28/16
to Repo and Gerrit Discussion

Am Freitag, 23. September 2016 17:17:45 UTC+2 schrieb Hugo Arès:
Gerrit version 2.13.1 is now available.

Unfortunately, OAuth extension point has an issue for OAuth providers that don't
expose user names (Google OAuth): [1]. In case you have upgraded and not
prepared for Gerrit downgrade, I have created emergency fix for gerrit.war and
uploaded it to the plugin site: [2].

We are working on the proper fix for this problem: [3].


Reply all
Reply to author
Forward
0 new messages