| tag | c6af10bacf6ad3ac6160008a116d181785559023 | |
|---|---|---|
| tagger | David Pursehouse <dpursehouse@collab.net> | Mon Mar 12 11:24:44 2018 +0900 |
| object | fcc90699fdec17b941a473221d228c832a533fc0 |
v2.14.7
| commit | fcc90699fdec17b941a473221d228c832a533fc0 | [log] [tgz] |
|---|---|---|
| author | Inderjot Kaur Ratol <inderjot.kaur.ratol@ericsson.com> | Fri Feb 23 09:20:41 2018 -0500 |
| committer | David Pursehouse <dpursehouse@collab.net> | Mon Mar 12 10:57:36 2018 +0900 |
| tree | a63fe1b0ce749ab763bb0b6229328cf92e9bf742 | |
| parent | e0072fdd7a6a1e8ca90d0546cf5817c651f658af [diff] |
Fix the missing DB entry in Gerrit DB Due to an unknown reason (still under investigation), a few of the new LDAP users were not able to login after first time because the Gerrit DB was missing one of the two entries needed to authenticate the user (the second entry is only needed for the users with non-null usernames). The entry with external Id - "gerrit:abc" was never inserted to DB in such cases whereas the entry with external id - "username:abc" was created resulting in an account creation for the user. This causes inconsistency in the DB. An account gets created in first login attempt and second attempt fails to create missing external id because the "username:abc" entry already exists causing the DB action to rollback. As this bug is very infrequent and hard to replicate, this change provides an after-fix for the issue i.e. fixes the problem when an entry is missing in Gerrit DB. It checks if there exists an account already for the given username and links the newly created external ID to that account. It prevents the need to manually enter the missing entries in DB to solve the issue. Bug: Issue 7652 Change-Id: Icd2fbf77971f00783277f88fa085ea1bc761878f
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 IRC channel on freenode is #gerrit. An archive is available at: echelog.com.
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 --recursive 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.