Forum Discussion
12 years ago
This is a bit more complicated, but I have used PsExec.exe (a SysInternals utility) to launch TestComplete/TestExecute on a remote machine from Jenkins. PsExec can run in the Jenkins background process with no problem and it has a parameter (-i) that allows interaction with the desktop on the remote machine. You just pass the TC/TE command line string to PsExec and it will return the exit code from TestComplete so you can determine pass/failure. The issue is getting the log back to Jenkins, so I use a shared folder and copy the log back as an artifact.
The first time you run PsExec you have to accept the EULA, so note the parameter in the popup window which is "/accepteula" I think to block it. You don't want that window coming up when Jenkins kicks it off. Otherwise PsExec won't work and you will not get any indication as to why.
http://technet.microsoft.com/en-us/sysinternals/bb897553
The first time you run PsExec you have to accept the EULA, so note the parameter in the popup window which is "/accepteula" I think to block it. You don't want that window coming up when Jenkins kicks it off. Otherwise PsExec won't work and you will not get any indication as to why.
http://technet.microsoft.com/en-us/sysinternals/bb897553