commit | 9f607fc3d22e591ce7d03718277197fcea80b3fe | [log] [tgz] |
---|---|---|
author | Klaus Aehlig <aehlig@google.com> | Mon Aug 14 14:10:38 2017 +0200 |
committer | Klaus Aehlig <aehlig@google.com> | Mon Aug 14 15:48:33 2017 +0200 |
tree | b655ad17b7c21fd602f496c68e675ba510b3ba42 | |
parent | b18c782d3170d235081f107ee411353e311e2ec0 [diff] |
replace build-flow-plugin by workflow-aggregator The build-flow-plugin is discontinued and has known vulnerabilities (see https://wiki.jenkins.io/display/JENKINS/Build+Flow+Plugin). So follow the recommended successor plugin. Change-Id: I3b38425ff40ff572c1c2d932f43daf196a3d3be2
This workspace contains the setup for the continuous integration system of Bazel. This setup is based on docker images built by bazel.
If you are a user of the CI system, you might be interested in the following document:
Make sure you have a Bazel installed with a recent enough version of it. Also make sure gcloud and docker are correctly configured on your machine. Only docker version 1.10 or later is supported.
More documentation:
init.sh
: initializes the whole CI platform. This may delete VMs and do other irreversible changes, so handle with care.vm.sh
: lets you control the machines (e.g. start/stop them, create/delete/reimage them), including the Jenkins controller and the executor nodes.