Details
-
Improvement
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Won't Do
Description
Recently my builds broke without modifying the job-dsl because I added a second JDK and therefore no "default JDK" was available. I was not aware of the issue.
It would be nice if the job-dsl-plugin creates a warning if there is only one JDK defined and there is no jdk(...) definition in the job dsl. It could advise to use jdk('defaultName') in the job-dsl to not change the behavior of the jobs if another jdk is defined in the jenkins tool installation.
Attachments
Activity
Benjamin Herbert
created issue -
Benjamin Herbert
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Description |
Recently my builds broke without modifying the job-dsl because I added a second JDK and therefore no "default JDK" was available. I was not aware of the issue. It would be nice if the job-dsl-plugin creates a warning if there is only one JDK defined and there is no jdk(...) definition in the job dsl. It could advise to use jdk('defaultName') in the job-dsl to not change the behavior of the jobs if another jdk is defined in the jenkins tool installation. |
Benjamin Herbert
made changes -
| Labels | jdk |
Benjamin Herbert
added a comment - I was too narrow-minded. Benjamin Herbert
added a comment - daspilker I am not sure what to chose when I close the issue, can you close it?
Benjamin Herbert
added a comment - daspilker I am not sure what to chose when I close the issue, can you close it? 
Daniel Spilker
made changes -
| Resolution | Won't Do [ 10001 ] | |
| Status | Open [ 1 ] | Resolved [ 5 ] |
Daniel Spilker
made changes -
| Status | Resolved [ 5 ] | Closed [ 6 ] |
I don't think that this is feasible. It would generate a lot of bogus warnings for all Python, Ruby, NodeJs, etc jobs that do not care about the JDK.