Forget this - for what I need, SecureASTCustomizer is perfect - I'm not worried about malicious use of those steps, just keeping people from stepping on their toes.
A. On Wed, Apr 6, 2016 at 2:07 PM, Andrew Bayer <andrew.ba...@gmail.com> wrote: > For my various experiments, I've got a way to contribute Pipeline code as > functions either from plugins or the global library, but I'd really like to > apply some restrictions to the code that can be included in those functions > - i.e., no "stage", no "node", no "parallel" most notably. It *feels* like > there should be a way to do that with script-security - anyone have any > ideas on that front? Could it be done at load/parse time rather than > runtime? > > A. > -- 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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPbPdOY7K8Cofbt5p_KQ9w-nP5OY5KEubzYY9%3Dp%3Dck64_%3DLhPw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
