On Wed, Apr 10, 2019 at 10:26 AM Mark Bidewell <[email protected]> wrote: > Scripts not permitted to use staticMethod > org.codehaus.groovy.runtime.DefaultGroovyMethods getAt java.util.List > java.util.Collection
Not sure I ever came across that particular bit of Groovy syntax before, but feel free to add an addition to the default whitelist for it. > The only way to add new signatures is to repeatedly run a script until a > failure point. This is painful when moving a script from a test environment > to a production environment. Cannot remember if this was filed or not. In principle it might be possible for Pipeline builds (not other uses of the Groovy sandbox) to pause after a rejection and wait for approval or cancellation. Tricky. > You cannot individually manage approved signatures. If a signature needs to > be removed, the only option is invalidating all approvals and repeatedly run > scripts to generate approvals. This is definitely a filed RFE. > Are there plans to improve the plugins usability? No particular plans that I know of. The general recommendation is to use Declarative Pipeline when possible, for which `script-security` is moot, or generally to avoid doing nontrivial work at the Groovy glue layer. -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1jKkjT%3D-uDQpskvYP9ze_Ody_mkEFGxZTxh_mr9k6v9A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
