| commit | 9730f0bcd12fc5640fa68240b2fa5d21c3154c75 | [log] [tgz] |
|---|---|---|
| author | Thomas Draebing <thomas.draebing@sap.com> | Thu Oct 10 14:34:12 2019 +0200 |
| committer | Thomas Draebing <thomas.draebing@sap.com> | Tue Oct 15 15:03:23 2019 +0200 |
| tree | 2d4b5059b7ece251fb00ebf28cf4b7ef91d27322 | |
| parent | e9a5dcb2f2eef825a0c7d053d7738900804dcd95 [diff] |
Add Jenkinsfile for verification pipeline So far the job for verifying changes in the `gerrit`-project was managed in the repository of the CI itself. These jobs were still using the by now deprecated workflow type. This change adds a Jenkinsfile to this project, which describes the build and test workflow to be executed by the CI. The job will be executed by a multibranch pipeline in the CI. Note, that the job described in the Jenkinsfile for now just starts other jobs that will verify and check the code style of the change as it was done so far in the `Gerrit-verifier-change`-job. It is planned to change that in the future. Notable changes to the `Gerrit-verifier-change`-job are: - The job will not check on which branch it runs. The Jenkinsfiles present in the different branches will have to contain the branch-specific code. - In pipelines Jenkins is very strict in which methods are allowed to be executed, since code can easily be added to a Jenkinsfile, which could execute malicious commands on the CI. To avoid to have to whitelist such methods in general, the code was adapted to only use allowed methods. - The job is now triggered by the `verifier-trigger`-job in the CI. Change-Id: I4d9ac3ebfd342243c6b7bf36186567e1b5175a4f
Gerrit is a code review and project management tool for Git based projects.
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 googlesource.com. There is a mirror of the repository on Github.
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.
The IRC channel on freenode is #gerrit. An archive is available at: echelog.com.
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 https://gerrit.googlesource.com/gerrit
cd gerrit && bazel build release
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>]
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.