commit | 48e16f744bd17dea07f2f6ab109e3990510f038f | [log] [tgz] |
---|---|---|
author | Damien Martin-Guillerez <dmarting@google.com> | Sat May 27 23:57:31 2017 -0700 |
committer | Damien Martin-Guillerez <dmarting@google.com> | Mon May 29 08:40:38 2017 -0700 |
tree | b73454c0b5d4c9e2eef7bf3c722e857059f9f347 | |
parent | fed6d1902d461da89d44ff7ec64ac727d8e6af5d [diff] |
Fix installation of Bazel on Windows [MSVC variant] - -msvc label appears twice in the name of the binary not once. The naming scheme is probably not what we want but until the naming scheme is fully fixed, fix the reimaging script. - Use releases.bazel.build instead of github (faster and more reliable). - Remove pre-0.5.0 codepath Change-Id: Ic3765f68b40ed2a08f0128acb781c8a6cd656798
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.