| commit | 909142f2c08881ed4f6a8011b2db34475f865711 | [log] [tgz] |
|---|---|---|
| author | Damien Martin-Guillerez <dmarting@google.com> | Sun Jul 16 00:04:47 2017 +0200 |
| committer | Damien Martin-Guillerez <dmarting@google.com> | Tue Jul 18 17:10:47 2017 +0200 |
| tree | e9f810eb9d0c927a5c67b87fe81b51a215010157 | |
| parent | 99705992b19cf5ced36fa1ecbe87e9513b692795 [diff] |
New pipeline: make release pipeline works The old pipeline was relying on some very peculiar layout of the files and that prevented to provide a build.log artifact. This change transfer the reponsibility of the layout from script/ci/build.sh (function bazel_release) to pushRelease. Change-Id: I59a3c33966bee769313fb8babe1bad3799f5b830
This workspace contains the setup for the continuous integration system of Bazel. This setup is based on docker images built by bazel.
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.