Hi, I too faced same problem. I tried runas . Also tried with variuos options of CMD in x32 and x64.
I am nost sure about actual casuse but I observed that My Jenkins was installed in x32 C:\Program Files (x86)\Jenkins\jobs\.... > > > > > Build\workspace > > > C:\Windows\TEMP\jenkins2333988544009686929.bat So I re-configured my Jenkins in x64 and the problem got resolved. I believe the *.bat file in TEMP uses the process as per Jenkins CPU x32 and this may be the reason. The program I tried to run via batch Command was an x64 program . I still need to investigate on how the TEMP\*.bat process works in Jenkins. Any help will be appreciated. Thanks. On Thursday, May 17, 2012 at 2:06:43 PM UTC+5:30, Lee Winder wrote: > > Hi Indyn > > I solved my problem by moving the executable calls outside of the build > process. I now have a few scripts constantly running in the background, > which the build process sends a message to when they want the executables > to run, and then waits for the executable scripts to flag back to the build > system that they have finished running and that it can continue. The build > system step for that is simply a small script which sends a message and > waits for receipt of another one, nothing more complicated than that. > > It's not an ideal solution as it takes the error reporting and console > output out of the build system so its more difficult to monitor, and this > permission error has happened a couple of times now so I have a number of > this constantly running scripts in the background. Any more and it'll > become difficult to maintain. > > This is my first experience of Jenkins, so I'm putting the issue down to > my lack of understanding in how the system works, but I don't think I'll > continue to use the system if this happens in the same way on future > projects. > > > > On Wednesday, 16 May 2012 17:27:06 UTC+1, Indyn wrote: >> >> Hello Lee and Jan, >> >> I am having a similar problem. My batch script was simply: >> ----- >> cd "C:\Installs\Win32Forth 6.14.00" >> start-both-RTests.exe >> ----- >> When I ran the job, the Console Output was: >> -------- >> Started by user anonymous >> Building on master in workspace C:\Program Files (x86)\Jenkins\jobs >> \Client Code1\workspace >> [workspace] $ cmd /c call C:\Windows\TEMP >> \hudson5297019636393332101.bat >> >> C:\Program Files (x86)\Jenkins\jobs\Client >> Code1\workspace>ClientCode1.bat >> >> C:\Program Files (x86)\Jenkins\jobs\Client Code1\workspace>cd "C: >> \Installs\Win32Forth 6.14.00" >> >> C:\Installs\Win32Forth 6.14.00>start-both-RTests.exe >> -------- >> Jenkins was hung (swirling symbol, flashing red dot beside Console >> Output) at the last line. >> >> I tried the runas, but it required a password to be entered >> interactively. I don't see how to do the runas in a script. >> >> Lee, did you get your exe to run? Any more hints or suggestions? >> >> Thanks, >> Indyn >> >> -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/ca1c079d-ba6f-4b77-a806-4703ea9edf49%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
