commit | 49c1ce8ae58a3268ebb6cf37835bacf2abfc3315 | [log] [tgz] |
---|---|---|
author | Damien Martin-Guillerez <dmarting@google.com> | Mon Jun 05 19:53:19 2017 +0200 |
committer | Damien Martin-Guillerez <dmarting@google.com> | Tue Jul 25 14:29:32 2017 +0200 |
tree | 552c6b96dadb2b207b4211cb9e4de06d93f2941d | |
parent | 6ecad65236ba2cc65f2cab7f69a79ac66ad41ae0 [diff] |
Enable to use configuration files from the repository The configuration files are currently checked into the CI system repository. However, they really belongs to the repository, they are the "blueprint" of what should be build and tested on the CI system. The file can be checked in either at .ci/${name}.json or at scripts/ci/${name}.json. Change-Id: I2f0dedf7378ccb85605d0aa22d354e74b5a06ff7
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.