Google Git
Sign in
gerrit / gerrit / 71dadf4a59f4dd08bea1a3c5b711970cbee235f5
commit71dadf4a59f4dd08bea1a3c5b711970cbee235f5[log] [tgz]
authorEdwin Kempin <ekempin@google.com>Wed Jan 05 14:59:15 2022 +0100
committerEdwin Kempin <ekempin@google.com>Wed Jan 05 15:40:40 2022 +0100
tree0e86ab6789ca9f10a32ef757662bf8b0f0768c91
parent8209457ecc75375d0da0c1c8cdc445ab92e2a01e [diff]
Migrate timestamps in comment framework to Instant, but not in Comment yet

The writtenOn field in the Comment class is not migrated to Instant yet.
This is because comments are stored as JSON in NoteDb and we must ensure
that the serialized format doesn't change when changing the type of the
writtenOn field. The comment serialization is done by GSON. This means
we must register a GSON serializer for Instant that produces that same
format. Adding this serializer and doing this migration is tracked by
issue 15525. This change updates all timestamps in the comment framework
that do not affect the serialization.

Bug: Issue 15070
Bug: Issue 15525
Signed-off-by: Edwin Kempin <ekempin@google.com>
Change-Id: I137e38f69e899d30a4a0ab3fe86d14d46007c3d4
15 files changed
tree: 0e86ab6789ca9f10a32ef757662bf8b0f0768c91
  1. .settings/
  2. .ts-out/
  3. antlr3/
  4. contrib/
  5. Documentation/
  6. e2e-tests/
  7. java/
  8. javatests/
  9. lib/
  10. modules/
  11. plugins/
  12. polygerrit-ui/
  13. prolog/
  14. prologtests/
  15. proto/
  16. resources/
  17. tools/
  18. webapp/
  19. polymer-bridges
  20. .bazelignore
  21. .bazelproject
  22. .bazelrc
  23. .bazelversion
  24. .editorconfig
  25. .git-blame-ignore-revs
  26. .gitignore
  27. .gitmodules
  28. .gitreview
  29. .mailmap
  30. .pydevproject
  31. .zuul.yaml
  32. BUILD
  33. COPYING
  34. INSTALL
  35. Jenkinsfile
  36. package.json
  37. README.md
  38. SUBMITTING_PATCHES
  39. version.bzl
  40. WORKSPACE
  41. yarn.lock
README.md

Gerrit Code Review

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

Build Status Maven Central

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 8 based Gerrit image:

    docker run -p 8080:8080 gerritcodereview/gerrit[:version]-centos8

To run a Ubuntu 20.04 based Gerrit image:

    docker run -p 8080:8080 gerritcodereview/gerrit[:version]-ubuntu20

NOTE: release is optional. Last released package of the version is installed if the release number is omitted.