commit | 340422c4b8e460b5b109e8bfb0a77d0740a483a6 | [log] [tgz] |
---|---|---|
author | David Pursehouse <dpursehouse@collab.net> | Fri May 11 09:30:26 2018 +0900 |
committer | Gerrit Code Review <noreply-gerritcodereview@google.com> | Fri May 11 00:32:50 2018 +0000 |
tree | 043cf0102afb64bc14fe5bf8e4e5b18c90778da8 | |
parent | b967f404734af31e286ed6f013e1cc7d96ef3445 [diff] |
Update git submodules * Update plugins/hooks from branch 'master' to da73b23cfb065fc28c9e7653860ccd34bd68f0f0 - Merge branch 'stable-2.15' * stable-2.15: More logging improvements to help tracking down hook problems Clarify usage of logging set-level command in documentation Update debug documentation to enable debugging for the whole package Change-Id: I86474c9fb38708a6b74570e4c91f8ef4c2ba834e - Merge branch 'stable-2.14' into stable-2.15 * stable-2.14: More logging improvements to help tracking down hook problems Clarify usage of logging set-level command in documentation Update debug documentation to enable debugging for the whole package Change-Id: I9d345784c32e4c682ea8110af9323934d8c2ce52 - More logging improvements to help tracking down hook problems Add more informational logs: - The configured hooks path. - The resolved path for each hook. Each of these is only logged once (the latter once per hook) so logging at info level will not be obtrusive. Log the path of the hook file if it does not exist. This is logged at debug level because it will be emitted on every attempt to execute the hook. Change-Id: I1fe6f860346d73648283178b58982180d2c35ce9 - Clarify usage of logging set-level command in documentation The command only works for existing loggers. To set the level for all loggers one must change the log4j configuration. Change-Id: I44c04a2fcae8d8c9e812e7de28cf4ccfd3c31b65 - Update debug documentation to enable debugging for the whole package Instead of only enabling for the HookTask class, enable for the whole hooks package. Change-Id: I33503f6185f07945f88b6de7a7aab4eaa509fbbf
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.