commit | 44e6c6c27adc3d7965c11f892f4f7c4f9ccef507 | [log] [tgz] |
---|---|---|
author | Damien Martin-Guillerez <dmarting@google.com> | Thu Aug 31 14:36:26 2017 +0200 |
committer | Damien Martin-Guillerez <dmarting@google.com> | Thu Aug 31 14:36:26 2017 +0200 |
tree | 6fb3a9dc7b120362bd16a0bf5fd7fac36c0335b7 | |
parent | fd0e79953a55caf0997b7a6bf3b9163917aa717a [diff] |
Clean-up before checkout Or if there is a file that is modified from the WORKSPACE, it will prevent checking out the new version of the file. Change-Id: I77bbc7084dbeedeb3fc52afd7fd36a28ab50e8cb
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.