Update git submodules

* Update plugins/replication from branch 'master'
  to 5622267e9fe339e185c6e80978b57100476d8f25
  - Remove unused private methods
    
    Change-Id: Ibad18b68f471bfb2e6fadaf1455993aa2d382d9d
    
  - Get a URI lock before running tasks.
    
    This allows more than one related gerrit process (as in multi-master
    situations) to access the persistent task store at the same time without
    deleting each other's task files. This also prevents more than one gerrit
    process from pushing to the same URI at the same time.
    
    Change-Id: I1f3f4d60605ff21038e722553cb38494e18b9ff9
    
  - Create persistent task files safely
    
    Use a temporary directory to create the files in first to avoid
    partially written files being exposed in the waiting directory.
    
    Change-Id: I82222e16b52926ced304cb24eadd1c8d56cf9a7a
    
  - Fix potential loss of persisted replication task
    
    There was a race window between the check to see if any new updates were
    available for the completed update and the deletion of the persistent
    update. If an update occurred in that window it could leave the event
    missing from the persisted task store. If the server went down before
    this update completed, the update would be missed entirely.
    
    Eliminate the race by separating the running tasks from the waiting
    tasks in the persistent store by placing each into their own
    subdirectories. Place new waiting tasks in a "waiting" directory and
    move them to the "running" directory once they are running. This allows
    new updates to be persisted to the "waiting" directory while a similar
    update is running without the waiting task getting deleted when the
    persisted running task is deleted. On startup, reset all running tasks
    by moving them back to the waiting directory to ensure that they are
    retried.
    
    Reset "running" tasks (return them to the "waiting" directory) when a
    retry is rescheduled, this allows the retry to be consolidated with the
    new run, and helps ensure that the persistence store reflects what is
    actually happening better.
    
    Bug: Issue 11672
    Change-Id: Ia31329e8d939f8e5cb1e7455de69744431f34d66
    
1 file changed
tree: b61851049d24d45403b90033685feb1429c64e2d
  1. .settings/
  2. antlr3/
  3. contrib/
  4. Documentation/
  5. e2e-tests/
  6. java/
  7. javatests/
  8. lib/
  9. modules/
  10. plugins/
  11. polygerrit-ui/
  12. prolog/
  13. prologtests/
  14. proto/
  15. resources/
  16. tools/
  17. webapp/
  18. .bazelignore
  19. .bazelproject
  20. .bazelrc
  21. .bazelversion
  22. .editorconfig
  23. .git-blame-ignore-revs
  24. .gitignore
  25. .gitmodules
  26. .gitreview
  27. .mailmap
  28. .pydevproject
  29. BUILD
  30. COPYING
  31. INSTALL
  32. Jenkinsfile
  33. package.json
  34. README.md
  35. SUBMITTING_PATCHES
  36. version.bzl
  37. 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 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 --recurse-submodules 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.