Update git submodules

* Update plugins/replication from branch 'master'
  to a62d1c601e6c7fb669c847a0e1843e6f60cd1cb2
  - Merge branch 'stable-2.15' into master
    
    * stable-2.15:
      GerritSshApi: Use Logger's string formatting
      Revert "Use proper HEAD ref value when creating project"
      Fix creating missing repository
      Fix project deletion logs
      Use logger built-in formatter
      Fix project creation logs
    
    Change-Id: I0c2c6c0638275e91c15d7c2871cb1c3cffa259c6
    
  - Merge branch 'stable-2.14' into stable-2.15
    
    * stable-2.14:
      Fix creating missing repository
      Fix project deletion logs
      Use logger built-in formatter
      Fix project creation logs
    
    Change-Id: Idacfd3fa54d7ff5e974bc8dae41979d1f0d9b6b5
    
  - GerritSshApi: Use Logger's string formatting
    
    Change-Id: Ie7fef1b311f6f7fe14aa79c6023b897d91127087
    
  - Revert "Use proper HEAD ref value when creating project"
    
    The issue fixed by this commit was fixed in a different way on the
    stable-2.14 branch. Reverting this on stable-2.15 will make the merge
    from stable-2.14 easier.
    
    This reverts commit e145010de7911623c98e6111537ffa4997d1a82e.
    
    Change-Id: I7e44f62f119b7ed26c8d96bfe9ef8442ff687b29
    
  - Fix creating missing repository
    
    When replicating to a destination where the repository does not exist,
    updating the HEAD reference failed because the passed reference name was
    not absolute. When this happened, an unchecked exception was triggered
    but never showed in the logs. In fact, the replication logs were showing
    only the message announcing the replication started, but no additional
    information about the success or failure of the operation was displayed.
    
    Avoid this by resolving symbolic references and checking the reference
    is absolute before trying to update the HEAD in the new repository.
    
    Change-Id: I18295a37a04413ba64bf7e9ee31640ee23c4c1e0
    
  - Fix project deletion logs
    
    Log was showing project was deleted successfully even if it failed.
    
    Change-Id: I7be19991619ce1f205884a8b6658d9a7ed4109c7
    
  - Use logger built-in formatter
    
    Change-Id: I6b46309f07ca4c402ae7a51cfb462c1be6bec333
    
  - Fix project creation logs
    
    Log was showing project was created successfully even if it failed.
    
    Change-Id: Ie37e6f2f58e1c8b4e33f61bf2d81ee43698b8aa3
    
1 file changed
tree: f3d9e0a893a7354031d2f9419b0db3943a4872e6
  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. resources/
  17. tools/
  18. webapp/
  19. .bazelproject
  20. .editorconfig
  21. .git-blame-ignore-revs
  22. .gitignore
  23. .gitmodules
  24. .mailmap
  25. .pydevproject
  26. BUILD
  27. COPYING
  28. INSTALL
  29. README.md
  30. SUBMITTING_PATCHES
  31. version.bzl
  32. 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.