00da932fab
Many of the acceptance test rely for their assertions on unique timestamps. This is achieved by setting a clock step. E.g. a clock step of one second means that two subsequent timestamps differ by 1 second. Test classes set the clock step in a setup method that is annotated with @Before or @BeforeClass, and then they reset the clock to use system time in a cleanup method that is annotated with @After or @AfterClass. On method level setting a clock step must have a finally block to unset it when the test is done. This results in a lot of boilerplate code and is also error-prone (e.g. some tests didn't reset the clock to use system time after setting a clock step). The new UseClockStep annotation makes this easier and less error-prone. If this annotation is set (either on class or method level) AbstractDaemonTest takes care to set and unset clock steps. By default @UseClockStep uses a clock step of 1 second, which is what most tests use, but the clock step and the clock step unit can be specified explicitly. In addition it's possible to request setting the clock initially to Instant.EPOCH which some tests require. If a test class uses a clock step single methods in this class can override this setting by using the UseSystemTime annotation. In addition this change adds a UseTimezone annotation that allows to set the timezone for the test execution. Here too using the annotation relieves the tests from caring to reset the timezone after the test is done. All tests that set a clock step or a timezone are adapted to use the new annotations. Signed-off-by: Edwin Kempin <ekempin@google.com> Change-Id: Iff0429cedadaea8538fd5ab96417241762f5a588
Gerrit Code Review
Gerrit is a code review and project management tool for Git based projects.
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.