Fork off a custom workspace_status.py with more heuristics

In some cases, the version description of plain `git describe` is not
ideal and could be improved by implementing a few of the common
conventions of our code base. Since implementing these conventions
might slow down stamping and we do not want to slow down the
development cycle for everybody, we fork off a dedicated
workspace_status with added heuristics.

Test plan:

  1. Make sure you're in branch stable-3.1

  2. Link stable-3.1 branch of `its-base` into plugins directory.

  3. Link stable-3.1 branch of `its-phabricator` into plugins directory.

  4. Verify that

   $ python tools/workspace_status.py | grep PHAB

 looks like

   STABLE_BUILD_ITS-PHABRICATOR_LABEL 407a93f

 (The stamp is the plain, abbreviated commit hash)

  5. Verify that

   $ python tools/workspace_status_release.py | grep PHAB

 looks like

   STABLE_BUILD_ITS-PHABRICATOR_LABEL stable-3.1-0-g407a93f(its-base:stable-3.1-0-g01c400e)

 (So it contains the `its-base` version, and exposes that both are on
 `stable-3.1`)

Change-Id: Ib1681b2730cf2c443a3cb55fe6e282f6484e18de
1 file changed
tree: 091d82bb121e773628f1d50a00cccc6868e9abe9
  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. .zuul.yaml
  30. BUILD
  31. COPYING
  32. INSTALL
  33. Jenkinsfile
  34. package.json
  35. README.md
  36. SUBMITTING_PATCHES
  37. version.bzl
  38. 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.