| commit | 0dd61c0d9704dfd468d5540bb6d47509b06bca66 | [log] [tgz] |
|---|---|---|
| author | Yun Peng <pcloudy@google.com> | Mon Jul 31 11:34:25 2017 +0200 |
| committer | Yun Peng <pcloudy@google.com> | Thu Aug 10 09:03:36 2017 +0000 |
| tree | d6a96afa6b0931f8a00060cb126b3ad1b2b0652a | |
| parent | 0b01e897bffe3f43789ab617e52fdf7c6b40c272 [diff] |
Don't run bazel_windows_example_test with MSYS toolchain anymore. Instead just using a //examples/cpp:hello-world to make sure the MSYS toolchain doesn't regress. bazel-tests.json has been moved to Bazel repo, this change is for old version source tree. Change-Id: Ic846dae0f3c249c7c8b436ec6c1bdf5edf54fd22
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.