We need to start verifying against JDK17 as we prepare to make the
switch to requiring JDK17.
Add a odl-maven-verify-jobs-jdk17 template and use it for
odlparent/master in addition to normal odl-maven-verify-jobs.
Since JDK17 is only available on CentOS8, also switch the build node
from default (which is still CentOS7).
JIRA: ODLPARENT-256
Change-Id: I4caa06d0e80c3e2a8c7e71a965af6202adca167d
Signed-off-by: Robert Varga <robert.varga@pantheon.tech>
rtd-token: e5afd4ac1ead64408d9e13cd1f628ade55512f8f
- odl-maven-jobs-jdk11
- odl-maven-verify-jobs
rtd-token: e5afd4ac1ead64408d9e13cd1f628ade55512f8f
- odl-maven-jobs-jdk11
- odl-maven-verify-jobs
+ - odl-maven-verify-jobs-jdk17
- gerrit-tox-verify
project: odlparent
- gerrit-tox-verify
project: odlparent
stream: master
branch: master
stream: master
branch: master
- java-version: "openjdk11"
mvn-settings: odlparent-settings
mvn-settings: odlparent-settings
+ build-node: centos8-builder-4c-4g
dependencies: ""
email-upstream: "[odlparent]"
dependencies: ""
email-upstream: "[odlparent]"
+- job-group:
+ name: odl-maven-verify-jobs-jdk17
+
+ jobs:
+ - gerrit-maven-verify
+ - gerrit-maven-verify-dependencies:
+ build-timeout: 180
+
+ mvn-version: mvn38
+ java-version: openjdk17
+
- job-template:
name: "{project-name}-integration-{stream}"
- job-template:
name: "{project-name}-integration-{stream}"