f377aa96de
This version includes a lot of new features and improvements, including: * Switched to top-down-building, which should generally make builds faster. The old behavior can be bypassed by passing --deep on the command line [1] * New query command was added (inspired by Bazel) [2] * Performance improvement in file globbing Extend tools/eclipse/project.py to pass the --deep option to ask Buck to execute bottom-up build when generating the Eclipse project. This is needed otherwise after using the buck clean command only the gerrit.war file would be fetched from the cache and the buck-out/gen/lib folder would remain empty. With [3] genrule output is now namespaced with the genrule name. Adapt documentation and references in the code to the new location of Buck artifacts. Because of this change, `buck clean` must be issued after Buck upgrade, otherwise the build would fail. The same prolem exists when switching between branches: `buck clean` must be issued, otherwise the build would fail. Test plan: * buck build release * buck build api_install * buck test * install and verify new gerrit site * upgrade and verify existing gerrit site * reindex existing gerrit site * verify that tools/eclipse/project.py produces sane Eclipse project * verify that unit test execution from Eclipse works * verify that daemon started from Eclipse works * verify that GWT SDM debug session started from Eclipe works [1]217cec33bc[2] https://buckbuild.com/command/query.html [3]c92ef212b5Change-Id: Ib3f22e70b7cb9eb9349618f2bcc018bf799c40f8
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 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 Buck and run the following:
git clone --recursive https://gerrit.googlesource.com/gerrit
cd gerrit && buck build all
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>]
NOTE: release is optional. Last released package of the version is installed if the release number is omitted.
Events
- November 7-8 2015: Gerrit User Conference, Mountain View. (Register).
- November 9-13 2015: Gerrit Hackathon, Mountain View. (Invitation Only).
- March 2016: Gerrit Hackathon, Berlin. (Details to be confirmed).