commit | e8722a10e30809b9adf5ee4e0194c35952244df8 | [log] [tgz] |
---|---|---|
author | Damien Martin-Guillerez <dmarting@google.com> | Tue Jun 27 18:11:47 2017 +0600 |
committer | Damien Martin-Guillerez <dmarting@google.com> | Tue Jul 11 21:24:30 2017 +0200 |
tree | 95ca4382cbf47e1a8f72e6bfe28eb49f0c9836d4 | |
parent | b83f958fffb30d8f3b97eac1dd55c9ca7e5ef648 [diff] |
bazelPath: use Jenkins magic to execute cleanup on the slave itself The current way of doing the work, we were cleaning-up the Jenkins master. Also overwrite destination when moving upstream artifact Change-Id: I7ad30e9e53fd682f72627ed00455eda9935055f8
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.