Bump Lucene version to 6.6.5 We cannot skip major Lucene version and upgrade directly from 5 to 7, because backwards codec compatibility layer only supports one major release. To support online reindexing we have to do the upgrade to Lucene 7 in two steps and wait for one gerrit release between the Lucene version upgrades. There are some removal and deprecation compared to current 5.5 version: * IntField, LongField are deprecated and supposed to be replaced with IntPoint and LongPoint. We use the deprecated Legacy<Foo> field types. These types were moved to Solr distribution and could be used even in the next major version 7. * TrackingIndexWriter functionality has been folded into IndexWriter in 6.2. Its APIs now return a long sequence number which can be passed to ControlledRealTimeReopenThread directly without TrackingIndexWriter acting as a mediator. Feature: Issue 7856 Change-Id: I25e8454e2b541eb5d8aac1e98d011c65b5e12240 
11 files changed
tree: 7a377c14b49bd9f4d0005e0cd86e2eded7e00dbd
  1. .settings/
  2. antlr3/
  3. contrib/
  4. Documentation/
  5. gerrit-gwtdebug/
  6. gerrit-gwtui/
  7. gerrit-gwtui-common/
  8. gerrit-plugin-gwtui/
  9. java/
  10. javatests/
  11. lib/
  12. plugins/
  13. polygerrit-ui/
  14. prolog/
  15. prologtests/
  16. proto/
  17. resources/
  18. tools/
  19. webapp/
  20. .bazelproject
  21. .bazelrc
  22. .editorconfig
  23. .git-blame-ignore-revs
  24. .gitignore
  25. .gitmodules
  26. .mailmap
  27. .pydevproject
  28. BUILD
  29. COPYING
  30. INSTALL
  31. README.md
  32. SUBMITTING_PATCHES
  33. version.bzl
  34. WORKSPACE
README.md

Gerrit Code Review

Gerrit is a code review and project management tool for Git based projects.

Build Status

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 IRC channel on freenode is #gerrit. An archive is available at: echelog.com.

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 --recursive 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.