| commit | 95a03ddfe807a2cc3c91ed8b7f3847f0e8784efc | [log] [tgz] |
|---|---|---|
| author | Damien Martin-Guillerez <dmarting@google.com> | Tue Aug 22 00:26:48 2017 +0200 |
| committer | Damien Martin-Guillerez <dmarting@google.com> | Wed Aug 23 13:22:21 2017 +0200 |
| tree | 1f0ece03490ea9098f45404e48cd25f0aaa09b1e | |
| parent | 4d629c59eb8cca946a6ae49af5c2cd4b0131045a [diff] |
Mark the global pipeline as unstable when new failures are found The current behavior made the status of the global pipeline mostly useless. It was introduced by 7bb4844547b580454848779d61f75e2c93ad3166 to not hide individual failure. However, individual failure are still visible AND still less interesting because without the before information, a failure can mean an existing failure. Change-Id: I5c49e0f60289afe708bb7d6688575f698f30aa18
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.