commit | a5df6b6825cf1fb0bd4c5fefaffaa410985b1479 | [log] [tgz] |
---|---|---|
author | Yun Peng <pcloudy@google.com> | Thu Jun 29 17:09:20 2017 +0200 |
committer | Yun Peng <pcloudy@google.com> | Fri Jun 30 11:10:31 2017 +0200 |
tree | 677769f197374ac6efb62f75897c4f6a1dbce32a | |
parent | 49d933d056c287345d84b020f6d447f5b1382854 [diff] |
Windows: use wrapper-free CROSSTOOL for bazel-tests Change-Id: I122d5b289dd619e0d7493a6b462829bb9bac8ae4
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.