-
Improvement
-
Resolution: Unresolved
-
Major
-
None
When using the conditional buildstep plugin it is not possible to select Scriptler as builder.
This seems to be related to JENKINS-15445: Conditional BuildStep only checks for builders with the @DataBoundConstructor annotation which is missing in the ScriptlerBuilder constructor. I already tried adding the annotation, so Scriptler becomes selectable. I can also set the groovy script to execute and the parameters, but: neither the "scriptId" nor the "parameters" are stored in the project! Funny though, the "propagateParams" flag is stored.
Using Scriptler as builder by it's own did work ok, by the way. I haven't done any further tests with the annotation and i actually don't know what "bad" influence it could have. And maybe the "unsaved" scriptId and parameters are related to some other bug.
- is duplicated by
-
JENKINS-22134 Add data-bound builder's constructor to support conditional build steps
-
- Closed
-
- is related to
-
JENKINS-36830 Implicit Groovy script args String[] is not recognized when scriptlet executes
-
- Open
-
Unfortunate this is not as easy as it might look. When saving a job configuration which contains a scriplter builder, then a check to see whether the user is actually allowed to change a scriptler configuration. If not, then the old scriplter-builder config is restored and only the parts of the job are updated. This check is currently not possible with a DataBoundConstructor and therefore I'm not able to implement this at the current time