commit | 129e36076f49f482419e2698cee2a216fbec0143 | [log] [tgz] |
---|---|---|
author | Yun Peng <pcloudy@google.com> | Fri Jul 21 09:53:20 2017 +0200 |
committer | Yun Peng <pcloudy@google.com> | Fri Jul 21 11:32:21 2017 +0000 |
tree | fe71e730a50183752cd748d0d88bf37a4f45eac2 | |
parent | 1e45eb3e41e7c742c68ef4c717135e44b681b7dd [diff] |
Add more Windows tests 1. Added C++ launcher tests for Windows binary laucher 2. Added //src/test/shell/bazel:bazel_windows_example_test into MSVC Bazel tests. Change-Id: I8702a883630a929c568ad3005e1e5363894e2aeb
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.