[JIRA] (JENKINS-36830) Implicit Groovy script args String[] is not recognized when scriptlet executes

[brunodepau...@yahoo.com.br (JIRA)]

Title: Message Title

Bruno P. Kinoshita commented on JENKINS-36830   Re: Implicit Groovy script args String[] is not recognized when scriptlet executes I believe the args you are seeing, is injected by Groovy by default. From: http://groovy-lang.org/structure.html#_public_static_void_main_vs_script A script is always compiled into a class. The Groovy compiler will compile the class for you, with the body of the script copied into a run method. Then the class that Groovy generates wrapping your script is similar to: import org.codehaus.groovy.runtime.InvokerHelper class Main extends Script { def run() { println 'Groovy world!' } static void main(String[] args) { InvokerHelper.runScript(Main, args) } } And [InvokeHelper](https://github.com/groovy/groovy-core/blob/master/src/main/org/codehaus/groovy/runtime/InvokerHelper.java) does the rest. But Scriptler and some other plug-ins that support Groovy create a GroovyScript from scratch *and also specify the BindingContext*. So you won't have the default args provided by Groovy. You will only get what the developer that is evaluating the Groovy script added to the context. I don't know how it could be implemented in Scriptler, to allow a Groovy script to be evaluated in the same manner by Groovy and by Scriptler. Perhaps it would be easier to just add support to Scriptler to the conditional step plugin... Add Comment   This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.