| commit | 7bb4844547b580454848779d61f75e2c93ad3166 | [log] [tgz] |
|---|---|---|
| author | Klaus Aehlig <aehlig@google.com> | Tue Aug 01 15:17:53 2017 +0200 |
| committer | Klaus Aehlig <aehlig@google.com> | Wed Aug 02 16:16:15 2017 +0200 |
| tree | bac2b05eb99eca012a657faa7c92ba4c5e2b8e33 | |
| parent | c5c0882823f0ff5b1ef12cc93f6db63545837e59 [diff] |
runAll: do not set global status, instead report individually
Setting the global status completely hides where the cause was.
However, for our use, we the main information is which downstream
project had problems, the difference between failure (as in "fails
to build") and unstable ("builds, but tests fail") is only secondary.
So, use the pipelines in a more standard way let individual jobs
report their individual failures---while still cathching the errors
and continuing with the final reporting step.
Change-Id: I8db14e81bcb33d5f902b16257748f38d44b09d39
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.