commit | 3e71872b5bcaf5935f288f4ea2e91f990425e211 | [log] [tgz] |
---|---|---|
author | Damien Martin-Guillerez <dmarting@google.com> | Fri Aug 25 15:38:00 2017 +0200 |
committer | Damien Martin-guillerez <dmarting@google.com> | Mon Aug 28 08:20:11 2017 +0000 |
tree | 9651f413462d70cf4f8ed7a74d0a8795c014f087 | |
parent | f4af155565dfc5baee0e51cc12dd4fab9d667ee6 [diff] |
Redirect the log of the slave to /root/jenkins-slave.log So a failure on that script can be investigated. Change-Id: If1834f8fda02881c88e9ce5e422b7acd963fcf50
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.