commit | 2d583d408b411fafe94ad9e6b4e86e05b43f8d79 | [log] [tgz] |
---|---|---|
author | Damien Martin-Guillerez <dmarting@google.com> | Fri Jul 28 13:14:16 2017 +0200 |
committer | Damien Martin-Guillerez <dmarting@google.com> | Fri Jul 28 13:52:42 2017 +0200 |
tree | cdb38e19629d020e984f565a9dd4b1b3722df7b1 | |
parent | c6cd4cd15b9119aef6f96766fd1af6a87a521f67 [diff] |
installBazel: Create the destination directory for Windows Fixes #113. Change-Id: I0b8c28a55a664c9b2b886800bdcb91835abb0c95
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.