Google Git
Sign in
gerrit / gerrit / 7d65712adcba93176304279972d9277c9d619924
commit7d65712adcba93176304279972d9277c9d619924[log] [tgz]
authorDavid Ostrovsky <david@ostrovsky.org>Sat Nov 11 05:38:03 2017 +0100
committerDavid Ostrovsky <david.ostrovsky@gmail.com>Sat Nov 11 14:52:04 2017 +0000
treef0814de8fc33fe9c2af34f5a90c4864bd133af62
parent7d35ff3fbeddc22fd2e0b42ff3f971598bba0c25 [diff]
Bazel: Don't ship version information in common:server artifact

Since I26e38a8c3 generated version information is included into
common:server artifact. This means that every time the generated
version is changed (the outcome of git describe command) the above
artifact is changed. As the consequence, almost all tests are
re-executed.

To rectify, isolate Version file in its own artifact and supply it
to tests and WAR packaging machinery. Don't bother to isolate the
version test in its own test rule, as there are only auto value
tests in addition to version tests. These two tests require 0.4 sec.
on my laptop. With this approach, every time, the new gerrit version
is generated, only common:server_tests rule is re-executed.

Bug: Issue 7737
Change-Id: Ib769c97ae651bdb347f5817ccc42e8dc52b5b975
3 files changed
tree: f0814de8fc33fe9c2af34f5a90c4864bd133af62
  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. website/
  20. .bazelproject
  21. .editorconfig
  22. .git-blame-ignore-revs
  23. .gitignore
  24. .gitmodules
  25. .mailmap
  26. .pydevproject
  27. BUILD
  28. COPYING
  29. INSTALL
  30. README.md
  31. SUBMITTING_PATCHES
  32. version.bzl
  33. 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.