Fix reporting for flaky builds in Jenkinsfile

The verification pipeline was not properly reporting the results of
builds that were suspect to being flaky. This happened, because the
build did not save the results in a variable, if the propagate option
was used, which had to be done for the pipeline plugin's retry command
to work.

Instead of using the retry-command provided by the pipeline plugin,
the Jenkinsfile implements this behaviour manually.

Bug: Issue 11927
Change-Id: I419a20f69cabc4c54d7f57fd04ad354563eafd71
1 file changed
tree: d1fbbfb567df8ccfed05c6cf7ffda63f3139468e
  1. .bazelignore
  2. .bazelproject
  3. .bazelrc
  4. .bazelversion
  5. .editorconfig
  6. .git-blame-ignore-revs
  7. .gitignore
  8. .gitmodules
  9. .mailmap
  10. .pydevproject
  11. .settings/
  12. 0001-Replace-native-http-git-_archive-with-Skylark-rules.patch
  13. BUILD
  15. Documentation/
  17. Jenkinsfile
  19. ReleaseNotes/
  22. contrib/
  23. gerrit-acceptance-framework/
  24. gerrit-acceptance-tests/
  25. gerrit-antlr/
  26. gerrit-cache-h2/
  27. gerrit-cache-mem/
  28. gerrit-common/
  29. gerrit-elasticsearch/
  30. gerrit-extension-api/
  31. gerrit-gpg/
  32. gerrit-gwtdebug/
  33. gerrit-gwtexpui/
  34. gerrit-gwtui-common/
  35. gerrit-gwtui/
  36. gerrit-httpd/
  37. gerrit-launcher/
  38. gerrit-lucene/
  39. gerrit-main/
  40. gerrit-oauth/
  41. gerrit-openid/
  42. gerrit-patch-commonsnet/
  43. gerrit-patch-jgit/
  44. gerrit-pgm/
  45. gerrit-plugin-api/
  46. gerrit-plugin-gwtui/
  47. gerrit-prettify/
  48. gerrit-reviewdb/
  49. gerrit-server/
  50. gerrit-sshd/
  51. gerrit-test-util/
  52. gerrit-util-cli/
  53. gerrit-util-http/
  54. gerrit-util-ssl/
  55. gerrit-war/
  56. lib/
  57. plugins/
  58. polygerrit-ui/
  59. tools/
  60. version.bzl
  61. website/

Gerrit Code Review

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

Build Status


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 There is a mirror of the repository on Github.

Reporting bugs

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.

Getting in contact

The IRC channel on freenode is #gerrit. An archive is available at:

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