-
Bug
-
Resolution: Unresolved
-
Minor
-
None
"default" JDK is the one present in user PATH - let's say JDK6
if I want to use an alternative JDK5, I declare it on system configuration
But I still can't edit my project configuration to select JDK and it still run with JDK6
I need to declare a 2nd JDK so that the select box appears and I can configure my JDK5 build.
I suggest to deprecate support for "Default" JDK, as this is confusing and dependent on host system configuration.
To ensure backward compatibility, jenkins could detect at startup jobs that don't have a <JDK> element in config and automatically create a "System" JDK in global configuration based on System.getProperty('java.home').
- is duplicated by
-
JENKINS-38911 Incorrect JDK tool version used for builds after new tool added
-
- Resolved
-
- is related to
-
JENKINS-755 Default JDK meaning in project options is confusing.
-
- Resolved
-
-
JENKINS-12550 System default JDK wrongly used if JDK is created first
-
- Resolved
-
Andreas: Please provide relevant config.xml from the affected jobs at the relevant points in time (as that will contain the JDK configuration even if hidden from UI). Your second job's issue does not appear to be possible if one JDK is configured system-wide.