• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • core
    • Jenkins 1.635

      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.

          [JENKINS-31217] No JDK named ‘null’ found in Jenkins 1.635

          I am still getting the error, but the failures were from a different issue which I've identified and fixed.

          Thanks.

          Vincent Caboara added a comment - I am still getting the error, but the failures were from a different issue which I've identified and fixed. Thanks.

          Jesse Glick added a comment -

          For the workaround you might need to create a dummy JDK so you can not select it. See JENKINS-10191 and JENKINS-17373.

          Jesse Glick added a comment - For the workaround you might need to create a dummy JDK so you can not select it. See JENKINS-10191 and JENKINS-17373 .

          If I explicitly configure JDK its JAVA_HOME is used by master and slave nodes. I can't have different JAVA_HOME for slaves.

          Igor Polubelov added a comment - If I explicitly configure JDK its JAVA_HOME is used by master and slave nodes. I can't have different JAVA_HOME for slaves.

          Thales Vieira added a comment -

          Temporary workaround: as jglick mentioned, go to the Global Settings, create add a JDK and not use it by default.
          With the JDK Plugin you can select the "Default" and it will stop failing.

          Thales Vieira added a comment - Temporary workaround: as jglick mentioned, go to the Global Settings, create add a JDK and not use it by default. With the JDK Plugin you can select the "Default" and it will stop failing.

          Daniel Beck added a comment -

          Adjusting priority as this only generates a useless message in the log, and has a workaround.

          Daniel Beck added a comment - Adjusting priority as this only generates a useless message in the log, and has a workaround.

          Sverre Moe added a comment -

          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

          Sverre Moe added a comment - 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

          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.

          SCM/JIRA link daemon added a comment - 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

          SCM/JIRA link daemon added a comment - 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

          Daniel Beck added a comment -

          Fixed towards 1.637.

          Daniel Beck added a comment - Fixed towards 1.637.

            wilfredh Wilfred Hughes
            mwebber Matthew Webber
            Votes:
            11 Vote for this issue
            Watchers:
            14 Start watching this issue

              Created:
              Updated:
              Resolved: