Hi Stan,
you may be in a situation where your second batch requires it's own VM when
spawning via Jenkins.
I came across this once until now because I have made some weird stuff from
Jenkins in operating system's admin context to access and modify services,
access the device manager from cli an
On 08/05/2012 23:30, de...@cpt.com wrote:
We are using winrs to remote shell from our Hudson instance to execute
a command on a remote windows server. The first winrs command
executes fine, the second winrs command never returns back to the
Batch Command being executed by Hudson. I executed the
Is Hudson running with same user as you ? When hudson batch file was
executed manually
-Raj
On Tue, May 8, 2012 at 11:42 PM, Vanlaeken, Eric
wrote:
> If your second command (the one that never returns) calls another batch
> file then you have to call your second batch file with a "call" command.
If your second command (the one that never returns) calls another batch
file then you have to call your second batch file with a "call" command.
Suppose you have a batch file named 1.bat that calls a file 2.bat then
the content of 1.bat should not be
2.bat
But
Call 2.bat
Greetings,
Eric
