commit | 286580afdc813a8b62043e5145431009f49ab188 | [log] [tgz] |
---|---|---|
author | Klaus Aehlig <aehlig@google.com> | Fri Aug 04 14:41:54 2017 +0200 |
committer | Klaus Aehlig <aehlig@google.com> | Fri Aug 04 16:17:25 2017 +0200 |
tree | f9a5885eb7fe967a19827b597b547ea9891e4d92 | |
parent | 18fc73a42ebff6b5f6d24b5c0390e0e3318a6884 [diff] |
Add links to sub-pipelines To simplify following subpipelines, add links to them in runAll. While it would be more useful to do so when starting the subpipeline, that would also be a lot harder. So let's do it at least after fact, as a first step. Helps towards #114. Change-Id: Ia2012fd084faa3938b22422752b57a74b1a584e1
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.