Forum Discussion

dcfecker's avatar
dcfecker
Contributor
8 years ago

TestExecute Jenkins job working last week, not working now

My Jenkins job was running great earlier last week. But the last few jobs the TestExecute is failing to start and the whole job fails.

 

I've tried running just TestExecute from the command line and it works. This will bring up TestExecute:

"C:\Program Files (x86)\SmartBear\TestExecute 12\bin\TestExecute.exe" 

 

But when I run the entire command line using TestCompleteService12 with expected user it does nothing, TesTexecute never comes up, just times out:

 

"C:\Program Files (x86)\SmartBear\TestExecute 12\bin\TestCompleteService12.exe" //LogonAndExecute //lDomain: "" //lName: "jenkins" //lPassword: ******** //lTimeout: "-1" //lUseActiveSession: "true" //lCommandLine: ""C:\Program Files (x86)\SmartBear\TestExecute 12\bin\TestExecute.exe" C:\jenkins\workspace\QATester_test1\LiveEarth_Smoke.pjs /run /SilentMode /ForceConversion /ns /exit /ExportLog:c:\jenkins\workspace\QATester_test1\3404378.tclogx /ExportLog:c:\jenkins\workspace\QATester_test1\3404378.htmlx /ErrorLog:c:\jenkins\workspace\QATester_test1\3404378.txt /ExportLog:c:\jenkins\workspace\QATester_test1\3404378.mht /DoNotShowLog"

 

If I disable the running TestCompleteService12 service hoping that it will start on it's own, I get an error saying that it's not running and needs to. 

2 Replies

  • Marsha_R's avatar
    Marsha_R
    Icon for Champion Level 3 rankChampion Level 3
    8 years ago

    Someone else may come along here and know more about Jenkins than I do, but what I would try is running as little as possible of that second string, maybe

     

    "C:\Program Files (x86)\SmartBear\TestExecute 12\bin\TestCompleteService12.exe"

     

    and see if it works.  Add on more options as you keep getting it to work.

     

    My guess is that either the permissions got changed on one of those directories or something got moved.

     

  • shankar_r's avatar
    shankar_r
    Community Hero
    8 years ago

    Hi,

     

    As you said, the same setup was running fine a week back.

    • Have you made any change in jenkins setup or upgraded?
    • Make sure before running jenkins build TestCompleteService12 service is running the salve since it will the service to trigger the TestExecute
    • There are chances when TestExecute not able to launch like below
      • License Server not available - Make sure you manually able to launch the TestExecute in slave
      • Not able to create a User Interactive Session - Check the setup in Advanced of TestCompelte build step
      • Permission issue.

    If above doesn't help to identify the issue, post here the Console output of jenkins build.

     

    P.S: If you run the entire command line manually you won't able to launch the TestExecute, there are some changes to needs to be run it manually which is not the issue here.