This is a Docker image based on the Jenkins Docker image that allows users to build and test the Gerrit CI jobs automatically, based on the configuration at https://gerrit.googlesource.com/gerrit-ci-scripts/
In turn, these CI scripts are based on http://docs.openstack.org/infra/jenkins-job-builder/ -- which builds Jenkins jobs based on YAML configurations.
In this particular image, the YAML configurations are updated and jobs reloaded every 5 minutes via the Jenkins SCM trigger. These jobs are fetched from the gerrit-ci-scripts repository and automatically reloaded.
It is also possible to run the gerrit-ci-scripts-manual job and provide the legacy Change ID number and a particular revision to build: Jenkins will fetch this particular change and load any job configurations changed in this revision. Note that it will not inhibit the main gerrit-ci-scripts trigger from polling.
If you're using boot2docker, the stock drive image and memory will not be enough. I would recommend growing your boot2docker volume to at least 40GB, and perhaps adding an extra 2-4GB swap space at the end of the volume. Additionally, you may wish to increase the amount of memory allocated to your boot2docker VM to at least 3GB (4GB+ preferred). Failing to do this may result in unusual failures of the VM or build errors.
For more information on enlarging the boot2docker volume, please see: https://docs.docker.com/articles/b2d_volume_resize/
Images available are:
gerritforge/gerrit-ci-slave: Base Jenkins slave with OS and prerequisites.
gerritforge/gerrit-ci-slave-debian: Base Jenkins slave with OS and prerequisites.
gerritforge/gerrit-ci-slave-buck: Buck build for older Gerrit until 2.13
gerritforge/gerrit-ci-slave-bazel: Bazel build for gerrit 2.14+.
gerritforge/gerrit-ci-slave-bazel-sbt: Setups scala for plugins that use scala.
gerritforge/gerrit-ci-slave-mvn - Setups maven for plugins that use maven.
If your not familar with docker please follow https://docs.docker.com/get-started/
Ask CI maintainer to generate for you unique slave id.
cat /proc/cpuinfo and report CI maintainer the number of CPUs, so that your slave would not get overloaded.
Clone gerrit-ci-scripts repository:
ppppackage is installed, e.g. on Ubuntu run:
Caution: Don't expose generic interface:
-H tcp://0.0.0.0:2375, otherwise, your Docker container could be hijacked.
In case your server is behind a Firewall, open tcp/2375 port for incoming requests.
Check on https://gerrit-ci.gerritforge.com and running
docker ps that your slave is up and running and build jobs are scheduled. If all went well and when jobs have arrived you should see something like: