Use remote Bazel Java11 JDK on Gerrit-CI for master
Gerrit-CI build agents do not have yet a local Java 11 setup
and therefore would still need to use a remote JDK provided
dynamically by Bazel.
Without the remote JDK, the acceptance tests would fail because
of class version incompatibility.
Change-Id: Ibe2f0a4b034354f42578a225e15689e1aed0969c
diff --git a/jenkins/gerrit-bazel-template.yaml b/jenkins/gerrit-bazel-template.yaml
index 6058c1e..769a08f 100644
--- a/jenkins/gerrit-bazel-template.yaml
+++ b/jenkins/gerrit-bazel-template.yaml
@@ -95,6 +95,12 @@
description: '{name} {branch} branch build with Bazel'
defaults: gerrit-bazel-defaults
node: bazel-debian
+ properties:
+ - inject:
+ properties-content: >
+ BAZEL_OPTS=--host_javabase=@bazel_tools//tools/jdk:remote_jdk11
+ --javabase=@bazel_tools//tools/jdk:remote_jdk11
+ --host_java_toolchain=@bazel_tools//tools/jdk:toolchain_java11
- project:
name: Gerrit-bazel
