Re: [workflow-plugin] Technical limitations for a workflow Groovy script

2015-02-25 Thread Jesse Glick
On Saturday, February 7, 2015 at 2:57:08 AM UTC-5, Baptiste Mathus wrote: I guess we'll need feedback of Jesse or Kohsuke as to where they want to go about that: filing JIRAs for classes to be whitelisted? There are so many obvious candidates that JIRA issues would be less than helpful, but

Re: [workflow-plugin] Technical limitations for a workflow Groovy script

2015-02-09 Thread Timur Batyrshin
Hi, To allow certain signatures in Groovy Sandbox go to Manage Jenkins - In-process Script Approval. Please note that if you catch this kind of exceptions the signatures will not appear there. Timur суббота, 7 февраля 2015 г., 10:57:08 UTC+3 пользователь Baptiste Mathus написал: IIUC, for

Re: [workflow-plugin] Technical limitations for a workflow Groovy script

2015-02-07 Thread Benjamin Muschko
On Saturday, February 7, 2015 at 2:46:12 AM UTC-5, Baptiste Mathus wrote: Hi, As the inline documentation (see the question marks on the right), this is because your code runs in sandboxed mode/you're not an admin: if *Use Groovy Sandbox* is checked, or you are not an administrator, not

Re: [workflow-plugin] Technical limitations for a workflow Groovy script

2015-02-06 Thread Baptiste Mathus
IIUC, for the moment only GStrings are whitelisted: see https://github.com/jenkinsci/workflow-plugin/blob/master/cps/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsWhitelist.java#L54 I guess we'll need feedback of Jesse or Kohsuke as to where they want to go about that: filing JIRAs for

Re: [workflow-plugin] Technical limitations for a workflow Groovy script

2015-02-06 Thread Baptiste Mathus
Hi, As the inline documentation (see the question marks on the right), this is because your code runs in sandboxed mode/you're not an admin: if *Use Groovy Sandbox* is checked, or you are not an administrator, not all APIs will be available. (Though I somehow agree that at first sight