commit | 16c7d2e60b77c5ee91bfde5809780ac2fadc9121 | [log] [tgz] |
---|---|---|
author | Laszlo Csomor <laszlocsomor@google.com> | Wed May 31 15:15:47 2017 +0200 |
committer | Laszlo Csomor <laszlocsomor@google.com> | Wed May 31 15:49:44 2017 +0200 |
tree | 1e418eca64204d2c4cc56093f1c1d4284b8af43b | |
parent | 00bc7f99a137153e49f21967546c028374cd1e31 [diff] |
Bazel-Install.bat.tpl: check %BAZEL_VERSION% Bazel-Install-Trigger #792 and Bazel-Install #16393 failed because %BAZEL_VERSION% was empty. (Why, I don't know.) Change-Id: I0d80c72726e436cf4f0e6fcc8e4b666327a8e14c
This workspace contains the setup for the continuous integration system of Bazel. This setup is based on docker images built by bazel.
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.