Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-31217

No JDK named ‘null’ found in Jenkins 1.635

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved (View Workflow)
    • Minor
    • Resolution: Fixed
    • core
    • 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

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-755 Default JDK meaning in project options is confusing.

          • Major - Major loss of function.
          • Resolved

          Activity

            Ascending order - Click to sort in descending order
            jglick Jesse Glick added a comment -

            Yes, the patch was incorrect. An original null check was dropped. I have commented in the PR.

            jglick Jesse Glick added a comment - Yes, the patch was incorrect. An original null check was dropped. I have commented in the PR.
            ct323i ct323i added a comment -

            Seeing No JDK named ‘null’ found between every step of the build.

            ct323i ct323i added a comment - Seeing No JDK named ‘null’ found between every step of the build.
            infiniteloop Vincent Caboara added a comment -

            Is there any sort of work around in the meantime?

            Thanks!

            infiniteloop Vincent Caboara added a comment - Is there any sort of work around in the meantime? Thanks!
            mwebber Matthew Webber added a comment -

            I rolled back to 1.634.
            However, the message might be benign (I'm not sure), in which case you could just ignore it. I can't say whether or not it's a real problem or not.

            mwebber Matthew Webber added a comment - I rolled back to 1.634. However, the message might be benign (I'm not sure), in which case you could just ignore it. I can't say whether or not it's a real problem or not.
            jglick Jesse Glick added a comment -

            Workaround should be to explicitly configure the JDK for the job.

            jglick Jesse Glick added a comment - Workaround should be to explicitly configure the JDK for the job.
            infiniteloop Vincent Caboara added a comment - - edited

            I have never had to set or configure a JDK for my Jenkins configurations, so I do not see a JDK option in the job.

            infiniteloop Vincent Caboara added a comment - - edited I have never had to set or configure a JDK for my Jenkins configurations, so I do not see a JDK option in the job.
            infiniteloop 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.

            infiniteloop 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.
            jglick 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.

            jglick 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 .
            halfwhite 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.

            halfwhite 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.
            thalesac 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.

            thalesac 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.
            danielbeck Daniel Beck added a comment -

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

            danielbeck Daniel Beck added a comment - Adjusting priority as this only generates a useless message in the log, and has a workaround.
            djviking 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

            djviking 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
            wilfredh Wilfred Hughes added a comment -

            Opened https://github.com/jenkinsci/jenkins/pull/1896

            wilfredh Wilfred Hughes added a comment - Opened https://github.com/jenkinsci/jenkins/pull/1896
            scm_issue_link 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.

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

            scm_issue_link 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
            danielbeck Daniel Beck added a comment -

            Fixed towards 1.637.

            danielbeck Daniel Beck added a comment - Fixed towards 1.637.

            People

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

              Dates

                Created:
                Updated:
                Resolved: