commit | 49f967c77e24acd993bec3fd6bf71ce1c8e8619c | [log] [tgz] |
---|---|---|
author | Damien Martin-Guillerez <dmarting@google.com> | Tue Aug 22 10:55:11 2017 +0200 |
committer | Damien Martin-Guillerez <dmarting@google.com> | Tue Aug 22 16:22:48 2017 +0200 |
tree | 42cadcf6dd01ab3f9330fbabe5e1b8bcdec74d13 | |
parent | bfb87c4242e116a6c886bdd11755c0ffe2c63c5d [diff] |
Fix the list of jobs to not exclude bazel-tests and bazel-docker-tests Change-Id: I5fdf5bd1017116ca5542a9a2c0b44a27a3d8a1e1
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.