-
Bug
-
Resolution: Fixed
-
Minor
-
-
Jenkins 2.126
See https://github.com/jenkinsci/configuration-as-code-plugin/issues/233
Currently the CasC plugin does not offer compatibility for old-style logic using @DataBoundConstructor. If a plugin configuration gets updated (new constructor, old is deprecated), the plugin just fails if newly introduced fields are non-null.
[JENKINS-51603] workDirSettings in JNLPLauncher requirements are too strict, CasC plugin is impacted
Assignee | New: Oleg Nenashev [ oleg_nenashev ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Status | Original: In Progress [ 3 ] | New: In Review [ 10005 ] |
Remote Link | New: This issue links to "https://github.com/jenkinsci/jenkins/pull/3463 (Web Link)" [ 20768 ] |
Remote Link | New: This issue links to "Workaround in JCasC (Web Link)" [ 20769 ] |
The actual issue is that JNLPLauncher's workDirSettings is declared @Nonnull https://github.com/jenkinsci/jenkins/blob/393680beb5d64628bdf8d9e5bf8daf4cab2191ad/core/src/main/java/hudson/slaves/JNLPLauncher.java#L69-L77 while it's actually nullable, as a default value can be safely computed (as done by deprecated constructor)
also read https://github.com/jenkinsci/jep/pull/111