commit | 8f36d5a829d69c489dc3e118e7047d78bf618fe4 | [log] [tgz] |
---|---|---|
author | Damien Martin-Guillerez <dmarting@google.com> | Mon Jul 24 23:00:23 2017 +0200 |
committer | Damien Martin-Guillerez <dmarting@google.com> | Tue Jul 25 16:07:00 2017 +0200 |
tree | 5694ff84523c7cad9d14638a6a851963e3411126 | |
parent | 2af2435c3c4ff8716aa4856b08e8f7f983858560 [diff] |
Correctly name of artifacts for the release Fixes #101 Change-Id: I0b0af821a617b4924ccfba17793387eed6fd2a7e
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.