-
Bug
-
Resolution: Fixed
-
Minor
-
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.
- is related to
-
JENKINS-755 Default JDK meaning in project options is confusing.
-
- Resolved
-
[JENKINS-31217] No JDK named ‘null’ found in Jenkins 1.635
Description |
Original:
Theory: This problem was introduced in Jenkins 1.635, as a result of the fix for 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 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. |
Link |
New:
This issue is related to |
Component/s | Original: maven-plugin [ 16033 ] | |
Assignee | New: Wilfred Hughes [ wilfredh ] | |
Labels | New: regression | |
Priority | Original: Minor [ 4 ] | New: Critical [ 2 ] |
Yes, the patch was incorrect. An original null check was dropped. I have commented in the PR.