Hi folks, runas has an option called /savecred. You would have to use runas once in the wanted user context and enter the credentials interactively. After that should it also work non-interactive.
HTH Jan Am Donnerstag, 17. Mai 2012 10:36:43 UTC+2 schrieb Lee Winder: > > 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 >> >>