• 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

          Matthew Webber created issue -
          Matthew Webber made changes -
          Description Original: Theory: This problem was introduced in Jenkins 1.635, as a result of the fix for JENKINS-755.

          I observer 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.
          New: 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.
          Matthew Webber made changes -
          Link New: This issue is related to JENKINS-755 [ JENKINS-755 ]

          Jesse Glick added a comment -

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

          Jesse Glick added a comment - Yes, the patch was incorrect. An original null check was dropped. I have commented in the PR.
          Jesse Glick made changes -
          Component/s Original: maven-plugin [ 16033 ]
          Assignee New: Wilfred Hughes [ wilfredh ]
          Labels New: regression
          Priority Original: Minor [ 4 ] New: Critical [ 2 ]

          ct323i added a comment -

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

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

          Is there any sort of work around in the meantime?

          Thanks!

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

          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.

          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.

          Jesse Glick added a comment -

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

          Jesse Glick added a comment - Workaround should be to explicitly configure the JDK for the job.

          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.

          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.

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

              Created:
              Updated:
              Resolved: