> Does the groovy plugin need anything special installed on the slaves?
there are two options, groovy script and system groovy script. First one
requires groovy installation on slaves (check global jenkins configuration,
auto-install can be used), second doesn't, however it's not executed on slave,
but in master JVM (it uses bundled groovy lib in the same way as you run
groovy script via groovy console)
> I can run the example 'println System.getenv("PATH")' in the jenkins
> script console for a slave but if I put the same thing in an 'execute
> groovy script''s groovy command box and run a build I get:
>
> [envtest] $ groovy
> e:\hudson\workspace\envtest\hudson782241948209548068.groovy The system
> cannot find the file specified
> FATAL: command execution failed
> java.io.IOException: Cannot run program "groovy" (in directory
> "e:\hudson\workspace\envtest"): CreateProcess error=2, The system
> cannot find the file specified
> at java.lang.ProcessBuilder.start(Unknown Source)
> [...]
>
> (default) is the only option for the groovy version.
