-
Bug
-
Resolution: Done
-
Major
-
4.13
-
2
-
False
-
None
-
False
-
Bug Fix
-
-
-
Pipeline Integrations #2260, Builds Sprint #2261, Builds Sprint #3
Description of problem:
Customer updated the Jenkins agent images from "ocp-tools-4/jenkins-agent-base-rhel8:v4.12.0" to "ocp-tools-4/jenkins-agent-base-rhel8:v4.13.0" and in this version switching Java versions by specifying the "USE_JAVA_VERSION" environment variable no longer works. We found the issue on GitHub (https://github.com/openshift/jenkins/issues/1712). Is this a bug or what is the correct way to define the Java version?
Version-Release number of selected component (if applicable):
ocp-tools-4/jenkins-agent-base-rhel8:v4.13.0
How reproducible:
Always
Steps to Reproduce:
1. As a Jenkins agent image, use "ocp-tools-4/jenkins-agent-base-rhel8:v4.12.0" and specify "USE_JAVA_VERSION=java-1.8.0" as an environment variable. 2. Observe that Java 8 is being used 3. Update the image to "ocp-tools-4/jenkins-agent-base-rhel8:v4.13.0"
Actual results:
USE_JAVA_VERSION is ignored, Java 11 is used
Expected results:
Same behaviour as with the older version.
Additional info:
- Upstream issue: https://github.com/openshift/jenkins/issues/1712
