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 <eric.vanlae...@barco.com>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. > > 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 > > -----Original Message----- > From: jenkinsci-users@googlegroups.com > [mailto:jenkinsci-users@googlegroups.com] On Behalf Of de...@cpt.com > Sent: Wednesday, 09 May, 2012 00:31 > To: Jenkins Users > Subject: Hudson - Execute windows batch command problems > > 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 bat file that > Hudson created and all the commands are executed successfully without > any pause/waiting. > > Has anyone come across this? Have a solution? I can split every > winrs into a separate Execute Batch Command, though, that is defeating > our requirements. > > Stan > > > DISCLAIMER: > Unless indicated otherwise, the information contained in this message is > privileged and confidential, and is intended only for the use of the > addressee(s) named above and others who have been specifically authorized > to receive it. If you are not the intended recipient, you are hereby > notified that any dissemination, distribution or copying of this message > and/or attachments is strictly prohibited. The company accepts no liability > for any damage caused by any virus transmitted by this email. Furthermore, > the company does not warrant a proper and complete transmission of this > information, nor does it accept liability for any delays. If you have > received this message in error, please contact the sender and delete the > message. Thank you. >