commit | 811c0bc11bf9f8cdfdac3ce1c6fb2356b2d7c254 | [log] [tgz] |
---|---|---|
author | Damien Martin-Guillerez <dmarting@google.com> | Sun May 28 14:26:00 2017 -0700 |
committer | Damien Martin-Guillerez <dmarting@google.com> | Thu Jun 08 07:45:46 2017 +0800 |
tree | de59ec6f8fb95aa00826bfbf43e45b5fb8f54446 | |
parent | 96e32ab96580f2df27d2e2891428127ae2d099d0 [diff] |
Replace usage of "node" by a custom step "machine" The node step does not output any information about the actual node, we have to go deep in the menu of Jenkins to find out which machine was selected. Change-Id: Ib8c1c6ea1f0d723f08a58e06d5af7029c8e28b6d
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.