commit | 9584fe457a7580c3dd3072c6c1e15b4a034e2bb5 | [log] [tgz] |
---|---|---|
author | Damien Martin-Guillerez <dmarting@google.com> | Wed Aug 23 18:16:53 2017 +0200 |
committer | Damien Martin-guillerez <dmarting@google.com> | Fri Sep 01 10:37:02 2017 +0000 |
tree | 5b8695824b724b0ef17c46bdc5eeea2be86ab431 | |
parent | 75b8520f441036e4f79e0478ea9a9365cc5e2125 [diff] |
Add a guide to explain where to look for information when monitoring bazel This is the correct fix for #114. Change-Id: Ie2ab1e54beee6b4a11f102457842c36c4e715184
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.