commit | 2764d560073f76f875af6eb8dd723845ac2b6e54 | [log] [tgz] |
---|---|---|
author | Damien Martin-Guillerez <dmarting@google.com> | Mon Jun 26 22:44:34 2017 +0600 |
committer | Damien Martin-Guillerez <dmarting@google.com> | Mon Jun 26 22:49:17 2017 +0600 |
tree | a1b01d42c0fe9512bcaeaeeb039748110d098a26 | |
parent | cc61248e40cd9ad7b9c98fcee4777d73a2e6e47c [diff] |
Exclude -jdk7 artifacts when doing the release For the next release we do not want to release JDK7 artifact, since the release is going to deprecate it, simply exclude the artifact from copy. This change does not remove any other JDK7 path, we will remove it once we passed one week with 0.5.2. Then we can allow introduction of JDK8 feature and kill all the code path for JDK7 :) Note: this is pretty hard to test so I will do a test release tomorrow morning with this change in, avoiding the necessity for another canary for 0.5.2. Change-Id: Ib450383a17af30f85fc82f5b314f80d6c107b514
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.