Hi, so I think I got this fixed: https://github.com/jenkinsci/groovy-plugin/pull/11 I still have a problem: When the configuration is reopened then all but the last radioBlock is not visible if there are multiple Groovy-Buildsteps. Any ideas? Moreover, the configuration page cannot be saved when the build-step is removed. When I deactivate the codemirror for the Groovy-Script text-area, then it works. This bug seems to be already present in the current version of the plugin.
Best regards, Stefan Am Freitag, 28. März 2014 18:59:33 UTC+1 schrieb Dominik Bartholdi: > > Stefan, > would be great to have this fixed, but I have no idea how to fix this in > stapler > Domi > > On 27.03.2014, at 23:06, Stefan Wolf <[email protected] <javascript:>> > wrote: > > Hi, > > today I ran into https://issues.jenkins-ci.org/browse/JENKINS-6797, and I > would like to fix the issue. > The issue seems to be that a DataBoundConstructor has one Parameter which > is an interface and therefore cannot be instantiated when used as embedded > Build Step by other plugins (in my case the conditional buildstep plugin). > The issue also states that before refactoring the groovy plugin one should > ask on the mailing list, if there is some way how Stapler can deal with > interfaces. > So has anybody an idea how to add this feature to stapler? > > Best regards, > Stefan > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <javascript:>. > For more options, visit https://groups.google.com/d/optout. > > > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
