commit | f4bd946633ff12907cd3edf8a9a3f0fb24135e5a | [log] [tgz] |
---|---|---|
author | Damien Martin-Guillerez <dmarting@google.com> | Mon Aug 21 22:11:37 2017 +0200 |
committer | Damien Martin-Guillerez <dmarting@google.com> | Wed Aug 23 13:22:21 2017 +0200 |
tree | e4ed8a8052b3a18f19d79aab5a0457e4c1f24512 | |
parent | e84c430eb75ad07f4c2136c3de7d86ea59fdb35a [diff] |
Use a pipeline job for the Benchmark job This delete the last non-pipeline job and should fix the issue with parsing XML files on the benchmark job. Change-Id: Iabc8e252e45c6f994f2c69cb17e67a019a442983
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.