-
Type:
Bug
-
Resolution: Not A Defect
-
Priority:
Critical
-
Component/s: groovy-plugin
-
None
-
Environment:Windows Server 2008 R2 (master)
Windows Server 2012 (slave)
While introducing Windows Server 2012 slaves into our Jenkins cluster, we encountered the following problem when executing Groovy scripts on them, which works fine on Windows Server 2008 R2 slaves:
Unpacking http://dl.bintray.com/groovy/maven/groovy-binary-2.4.0.zip to C:\Jenkins\data\tools\hudson.plugins.groovy.GroovyInstallation\Groovy_240 on js003 [dhs-test] $ C:\Jenkins\data\tools\hudson.plugins.groovy.GroovyInstallation\Groovy_240\groovy-2.4.0\bin\groovy.bat C:\Jenkins\data\workspace\dhs-test\hudson6031727683686272876.groovy Access is denied FATAL: command execution failed java.io.IOException: Cannot run program "C:\Jenkins\data\tools\hudson.plugins.groovy.GroovyInstallation\Groovy_240\groovy-2.4.0\bin\groovy.bat" (in directory "C:\Jenkins\data\workspace\dhs-test"): CreateProcess error=5, Access is denied at java.lang.ProcessBuilder.start(Unknown Source) at hudson.Proc$LocalProc.<init>(Proc.java:244) at hudson.Proc$LocalProc.<init>(Proc.java:216) at hudson.Launcher$LocalLauncher.launch(Launcher.java:803) at hudson.Launcher$ProcStarter.start(Launcher.java:381) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1136) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1101) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:328)
This was tested with Jenkins versions 1.543 and 1.598 as master, both running on Windows Server 2008 R2.
