| commit | 0db9b06b16e5e6d4d18efa4c5cd5fe70335ca9ba | [log] [tgz] |
|---|---|---|
| author | Damien Martin-Guillerez <dmarting@google.com> | Fri Sep 01 14:07:36 2017 +0200 |
| committer | Damien Martin-guillerez <dmarting@google.com> | Fri Sep 01 15:09:42 2017 +0000 |
| tree | c6b759e83b0415c227e40e52dd5a2a9f46344198 | |
| parent | 9584fe457a7580c3dd3072c6c1e15b4a034e2bb5 [diff] |
Remove duplicate options in the .bazelrc file creation Change-Id: Ia6ef22501646d5dcd819c9e30f3688284ca5af38
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.