Details
-
Bug
-
Status: Resolved (View Workflow)
-
Minor
-
Resolution: Fixed
-
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
-
JENKINS-755 Default JDK meaning in project options is confusing.
-
- Resolved
-
Activity
Matthew Webber
created issue -
Matthew Webber
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Description |
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. |
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. |
Matthew Webber
made changes -
| Link |
This issue is related to |
| Component/s | maven-plugin [ 16033 ] | |
| Assignee | Wilfred Hughes [ wilfredh ] | |
| Labels | regression | |
| Priority | Minor [ 4 ] | Critical [ 2 ] |
| Priority | Critical [ 2 ] | Minor [ 4 ] |
| Resolution | Fixed [ 1 ] | |
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Workflow | JNJira [ 166445 ] | JNJira + In-Review [ 197996 ] |
