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
-
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