Details
-
Bug
-
Status: Resolved (View Workflow)
-
Minor
-
Resolution: Fixed
-
Jenkins 1.635
Description
Theory: This problem was introduced in Jenkins 1.635, as a result of the fix for JENKINS-755.
I observe numerous No JDK named ‘null’ found messages in the job log for many jobs. The message looks like it is generated during the post-build steps.
Attachments
Issue Links
- is related to
-
JENKINS-755 Default JDK meaning in project options is confusing.
-
- Resolved
-
Activity
Wilfred Hughes
added a comment - Opened https://github.com/jenkinsci/jenkins/pull/1896 Code changed in jenkins
User: Wilfred Hughes
Path:
core/src/main/java/hudson/model/JDK.java
core/src/test/java/jenkins/model/JDKNameTest.java
http://jenkins-ci.org/commit/jenkins/707d4ba135ec9e3e6a681f1acb4e243e2b5aa9b6
Log:
JENKINS-31217 Treat null as a default JDK name.
Code changed in jenkins
User: Daniel Beck
Path:
core/src/main/java/hudson/model/JDK.java
core/src/test/java/jenkins/model/JDKNameTest.java
http://jenkins-ci.org/commit/jenkins/a2d9b797ec269e92a01a111887bef93e023a5f24
Log:
Merge pull request #1896 from Wilfred/jenkins-31217
JENKINS-31217 Treat null as a default JDK name.
Compare: https://github.com/jenkinsci/jenkins/compare/505fde00125c...a2d9b797ec26
I have the same problem with a Multi-configuration project where there is no option of selecting a JDK. Its output is right after starting builders and publishers from a template project (which are also a Multi-configuration project).
[TemplateProject] Starting builders from: template-project
No JDK named ‘null’ found
[TemplateProject] Starting publishers from: template-project-publishers
No JDK named ‘null’ found