commit | fd0e79953a55caf0997b7a6bf3b9163917aa717a | [log] [tgz] |
---|---|---|
author | Damien Martin-Guillerez <dmarting@google.com> | Thu Aug 31 13:43:33 2017 +0200 |
committer | Damien Martin-Guillerez <dmarting@google.com> | Thu Aug 31 13:43:48 2017 +0200 |
tree | 0c7a9b404ccbaa43f2257506a7d3a3bff09dc2e0 | |
parent | 4b1aa8b48a7d642cccb2ba78f202c25cb06e6c46 [diff] |
Revert "Make the repository compatible with the future versions of Bazel" This reverts commit 82df6bcd3897eaa149ac264f03439c76fba5794f. Break bazel run //gcr:deploy Change-Id: I1b67615b0fb183d1b985effaabca5adaa9ca4720
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.