| commit | fa25ee3d7d09487fd1fc82b1741bdf14b9b5c343 | [log] [tgz] |
|---|---|---|
| author | Damien Martin-Guillerez <dmarting@google.com> | Thu May 25 17:32:23 2017 -0700 |
| committer | Damien Martin-Guillerez <dmarting@google.com> | Fri May 26 15:13:35 2017 -0700 |
| tree | 3d8e12987c3c5f13a14f4a515394ed9a7022f178 | |
| parent | 8afb8db483c1048043533a7f110a8578a3333b4b [diff] |
Various fixes on the pipeline
- Fix a syntax error. Maybe we could detect them with a build test but
we need to figure out how to ship Jenkins dependencies on the class path.
- Nit: arranged the formatting of BazelUtils
- Nit: remove duplicate null affectation
- Fix the path to bazel, on freebsd it is a symlink from
~/.bazel/latest/binary/bazel and ~/.bazel/latest/bin/bazel does not exists
- Applies the -with{,out}-jdk patch to the bootstrap groovy.
With all those fixes here what is not yet working on the global pipeline:
- Windows MSYS fails because it expects a cpu that is in 0.5.0
- Windows MSVC fails because it expects a path that will be there after 0.5.0
So waiting for tomorrow's release and will continue to debug the pipeline.
Change-Id: Iec63cad686d28b93ff127d6bb1e7b1c4cd730f21
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.