• 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 made changes -
          Component/s Original: maven-plugin [ 16033 ]
          Assignee New: Wilfred Hughes [ wilfredh ]
          Labels New: regression
          Priority Original: Minor [ 4 ] New: Critical [ 2 ]
          Daniel Beck made changes -
          Priority Original: Critical [ 2 ] New: Minor [ 4 ]
          Daniel Beck made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 166445 ] New: JNJira + In-Review [ 197996 ]

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

              Created:
              Updated:
              Resolved: