Forum Discussion
12 years ago
We had a similar problem running via vmware. We resolved our problems doing this by running:
call "C:\Program Files (x86)\VMware\VMware VIX\vmrun" -T esx -h https://esxmachine/sdk -u %ENV_USER% -p %ENV_PASSWORD% -gu %ENV_GUEST_USER% -gp %ENV_GUEST_PASSWORD% runProgramInGuest "[Datastore] VMNAME/VMNAME.vmx" -activeWindow -interactive "<insert path to TC or bat file calling TC here>"
The key being the -interactive, without it we got the same symptoms as above. No registry hack needed. Of course the nicer solution would be making these client machines have jenkins installed but we're not there yet.
Next step: reporting the results of the tests nicely within Jenkins and automatically logging JIRA tickets when failures occur (plugin for jenkins will do that though)
call "C:\Program Files (x86)\VMware\VMware VIX\vmrun" -T esx -h https://esxmachine/sdk -u %ENV_USER% -p %ENV_PASSWORD% -gu %ENV_GUEST_USER% -gp %ENV_GUEST_PASSWORD% runProgramInGuest "[Datastore] VMNAME/VMNAME.vmx" -activeWindow -interactive "<insert path to TC or bat file calling TC here>"
The key being the -interactive, without it we got the same symptoms as above. No registry hack needed. Of course the nicer solution would be making these client machines have jenkins installed but we're not there yet.
Next step: reporting the results of the tests nicely within Jenkins and automatically logging JIRA tickets when failures occur (plugin for jenkins will do that though)