commit | bae7f95426892bc6b0c3cf1b1eb56d07c0021488 | [log] [tgz] |
---|---|---|
author | Damien Martin-Guillerez <dmarting@google.com> | Sun Jun 04 21:39:37 2017 +0200 |
committer | Damien Martin-Guillerez <dmarting@google.com> | Thu Jun 08 07:56:32 2017 +0800 |
tree | ac219807cad34acdb3f0bfa50a467b08cf9e84b8 | |
parent | 811c0bc11bf9f8cdfdac3ce1c6fb2356b2d7c254 [diff] |
Use a global install location for custom bazel The previous method was generating file system error on windows. Bazel is now installed into <bazel-installs>/custom/<project>/<build-number>/variation_<variation> and a task delete every file that have not been used for 2 days after we actually touch the last modification date. Change-Id: Icf2e2b2e5bc990cdffac99ac868a0855f5aea6ad
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.