| commit | 954a91d51ab72c64f587f2080f10be7484d87511 | [log] [tgz] |
|---|---|---|
| author | Matthias Sohn <matthias.sohn@sap.com> | Fri Apr 08 14:19:51 2016 +0200 |
| committer | David Pursehouse <dpursehouse@collab.net> | Mon Aug 13 11:42:43 2018 +0100 |
| tree | e2de7a824c85931bcde2dc9fbfb9eb542d9e2284 | |
| parent | e29bcbb0b4e19e745c93814533cae8e9107bad65 [diff] |
Upgrade JGit to 4.3.0.201604071810-r this version brings the following fixes - Fix jgit gc which retained garbage packs for 2 weeks which resulted in repo size explosion [1] by introducing a new option for pack expiration which by default expires packs after 1 hour - Fix refcounting and reclaiming memory in RepositoryCache. Hugo validated that this reduces memory consumption in Gerrit considerably - Make the FileLfsRepository thread safe. This fixes a severe threading issue for the lfs-storage-fs plugin [2] Requires disabling atomic updates on InMemoryRepositoryMangers used by acceptance tests because of this change [3] in JGit, lines 269-286. This creates an anonymous subclass of BatchRefUpdate and when running Gerrit's tests the code always enters the if-branch which doesn't update the progress monitor. Since the progress monitor is not updated the "refs: 1" is missing from the output and the assertion in the line 469 fails. When running normal (not from tests) Gerrit daemon this JGit code is not used and the issue doesn't exist. This is an intermediate step to upgrading to 4.5.4.201711221230-r which keeps the branch building and tests passing. Atomic update bug description re-worded from Saša Živkov's comment on [4]. [1] https://groups.google.com/forum/#!searchin/repo-discuss/gc/repo-discuss/JW06GsH0vLo/9GV4TL0VDgAJ [2] https://git.eclipse.org/r/#/c/52177/16/org.eclipse.jgit.lfs.server/src/org/eclipse/jgit/lfs/server/fs/FileLfsServlet.java [3] https://git.eclipse.org/r/#/c/61841/2/org.eclipse.jgit/src/org/eclipse/jgit/internal/storage/dfs/InMemoryRepository.java [4] https://gerrit-review.googlesource.com/c/gerrit/+/77110/1/gerrit-acceptance-tests/src/test/java/com/google/gerrit/acceptance/git/AbstractPushForReview.java#b496 Change-Id: If6ba90c5e79747d20338ad32f03624a6bd75ee43 Signed-off-by: Matthias Sohn <matthias.sohn@sap.com>
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 Buck and run the following:
git clone --recursive https://gerrit.googlesource.com/gerrit
cd gerrit && buck 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>]
NOTE: release is optional. Last released package of the version is installed if the release number is omitted.