could you try adding in 'executorType': 'TE' into your build stage?
Otherwise if you have followed the documentation to prepare the jenkins nodes, I don't see why you should be getting the -10 exit code;
also if you could post the full console logs of the failure message from that build step that would be helpful as well
Hello, hkim5!
Thanks for your reply. So, Isn't 'TE' the default value for executorType? Anyway, I'll change it to see if works.
About the log, It's attached in this reply.
Thanks a lot for your help!
ok throwing out some ideas
First can you remote into those Jenkins execution nodes and go into services to find the Jenkins-slave service?
Within properties-logon tab you should see that the below setting is shown with the checkbox enabled
Also- make sure that the credentialsID field that you provided within your pipeline script (with the variable you set as "cred" has admin credentials on those execution machines)
---------------
also worth mentioning: make sure that TestComplete 14 service is also running on the execution machines. Browser the documentation here to troubleshoot to see if firewalls or antivirus is blocking that service from running on the execution machines.
---
Then also go into the file explorer to find the directory where your testexecute executable is installed on those execution machines (by default, this should be "C:\Program Files (x86)\SmartBear\TestExecute 14\x64\Bin\")
rightclick select properties on the exe and change the compatibility settings such that you run the program as an admin for all users
Then go into the security tab of the exe and make sure that you have granted full rights to the system user (or any other user creds you would be using to start up the active user session)
also worth mentioning is to make sure that TestComplete 14 service is running on those execution machines (you can also check by going into "services") you can check the documentation here to troubleshoot to see if there are firewall rules or antiviruses that are preventing that service from running on your execution nodes
I did most of your suggestions and it still not working. I'm applying the firewall rules now, but I think that is not the problem, because, if I log in those machines by RDP and start the tests in jenkins, it works. That is, I think that the problem occurs when jenkins tries to create an interactive session.
The services were configured correctly like your suggentions, but, the executable's permissions not. I adjusted it, but, it still not working.
When I create the firewall rules and test it, I come back here to post the result.
Thanks!
