commit | 82df6bcd3897eaa149ac264f03439c76fba5794f | [log] [tgz] |
---|---|---|
author | Vladimir Moskva <vladmos@google.com> | Tue Aug 29 15:54:16 2017 +0200 |
committer | Vladimir Moskva <vladmos@google.com> | Tue Aug 29 20:14:26 2017 +0200 |
tree | 3e745603fe4cceaadb7c74a92b86185346af554a | |
parent | 0cdb20d1581dd5bdaa40b7fb0844cd67e2e80468 [diff] |
Make the repository compatible with the future versions of Bazel Change-Id: Ia9b3f6e8d75a4898fbc71690cd518e8ca003850e
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.