policy jobs must use JDK 11 for sonar/clm

Sonar job failing because we upgraded this repo to JDK 11
and forgot to set that job correctly. Also fixing CLM job.

I do not think the INFO.yaml needs this as its only checking
the .yaml file and not compiling the repo. Jessica please
confirm.

Issue-ID: POLICY-1406
Change-Id: I0a936bd4d4a0843e9443438e974071d99cb4e4ee
Signed-off-by: Pamela Dragosh <pdragosh@research.att.com>

diff --git a/jjb/policy/policy-common.yaml b/jjb/policy/policy-common.yaml
index 3ac5b25..ec7d783 100644 (file)
--- a/jjb/policy/policy-common.yaml
+++ b/jjb/policy/policy-common.yaml
@@ -37,6 +37,7 @@
     project-name: 'policy-common'
     branch: 'master'
     mvn-settings: 'policy-common-settings'
+    java-version: openjdk11
     mvn-goals: 'clean install'
     mvn-opts: '-Xmx1024m -XX:MaxPermSize=256m'
 
@@ -49,6 +50,7 @@
     project-name: 'policy-common'
     branch: 'master'
     mvn-settings: 'policy-common-settings'
+    java-version: openjdk11
 
 - project:
     name: policy-common-info

diff --git a/jjb/policy/policy-parent.yaml b/jjb/policy/policy-parent.yaml
index dca2452..86a5326 100644 (file)
--- a/jjb/policy/policy-parent.yaml
+++ b/jjb/policy/policy-parent.yaml
@@ -31,6 +31,7 @@
     project-name: 'policy-parent'
     branch: 'master'
     mvn-settings: 'policy-parent-settings'
+    java-version: openjdk11
 
 - project:
     name: policy-parent-info