Forum Discussion
Aha, well it seems like the TestCompleteService had stopped. It seems to that quite often which gives us a headache, since we have like 20 jenkins-slaves and manually logging into and checking them all the time is not a sustainable solution. I'll see if we can configure the service to restart on failure (if it is not already set up to do that).
Thanks!
JohanH if the services is crashing frequently, you should look into your logs. We have a similar environment with Jenkins executing TestExecute on our slave nodes and this has never been an issue for us.
The only time I have ever seen the TestComplete Service not running was when I accidentally killed it myself because I didn't realize that it was a service, and thought it was just left in memory after closing out TestExecute on a machine. Needless to say, I realized quite quickly that that wasn't the case.
Related Content
Recent Discussions
- 3 days agoMW_Didata