commit | 4b1aa8b48a7d642cccb2ba78f202c25cb06e6c46 | [log] [tgz] |
---|---|---|
author | Damien Martin-Guillerez <dmarting@google.com> | Wed Aug 30 10:37:31 2017 +0200 |
committer | Damien Martin-guillerez <dmarting@google.com> | Thu Aug 31 11:38:07 2017 +0000 |
tree | d27d8cd71f34ddccefecf6666590bb6419190de9 | |
parent | 82df6bcd3897eaa149ac264f03439c76fba5794f [diff] |
Add rules_k8s and rules_docker to our CI Also remove the rules_apple and create a generic empty configuration file so we can start by adding project and adapt the configuration file depending on the project using PRs to the project. Change-Id: Ia62c37bf058d3be197745fa2e4216a3dd82b8469
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.