Forum Discussion

Fimbultyr's avatar
Fimbultyr
Contributor
5 years ago

Jenkins TestCompletePlugin failing after update to 2.4

Hi there,

 

We are currently updating our Jenkins Server and installed the latest TestCompletePlugin with Version 2.4

Sadly the Testruns keep failing now.

 

Our Jenkinsfile looks like this and was not changed

stage("Test Job") {
					checkout([$class: 'GitSCM', branches: [[name: '*/master']], doGenerateSubmoduleConfigurations: false, extensions: [], submoduleCfg: [], userRemoteConfigs: [[credentialsId: 'mylovelycreds', url: 'https://github.mylovelycompany.com/mylovelyproduct/testcomplete.git']]])
					sleep time: 10, unit: 'SECONDS'
					testcompletetest actionOnErrors: 'MAKE_FAILED', actionOnWarnings: 'MAKE_UNSTABLE', executorType: 'TE', generateMHT: true, launchType: 'lcProject', project: 'mylovelyproduct Server', suite: 'mylovelyproduct.pjs', useTCService: true, userName: 'mylovelyfakeusername', userPassword: 'mylovelyfakepassword', timeout: '10800', useTimeout: true
				}

 

In the Logs we noticed that the Parameters used for execution have changed.
TestCompletePlugin 2.2

[TestComplete] The test execution started (MyLovelyProduct/MyLovelyProduct Server).
[TestComplete] Found TestComplete/TestExecute installations:
	Type: TE, Version: 14.30.3743.11, Path: "C:\Program Files (x86)\SmartBear\TestExecute 14\x64\bin\TestExecute.exe"
[TestComplete] Selected TestComplete/TestExecute installation:
	Type: TE, Version: 14.30.3743.11, Path: "C:\Program Files (x86)\SmartBear\TestExecute 14\x64\bin\TestExecute.exe"
[TestComplete] Launching the test runner.

$ '"C:\Program Files (x86)\SmartBear\TestExecute 14\bin\TestCompleteService14.exe"' //LogonAndExecute //lDomain: "" //lName: "MyLovelyProduct" //lPassword: ******** //lTimeout: "10980000" //lUseActiveSession: "true" //lCommandLine: '""C:\Program Files (x86)\SmartBear\TestExecute 14\x64\bin\TestExecute.exe" "c:\ProgramData\Jenkins\workspace\Sandbox\TestComplete Scripted Pipeline\MyLovelyProduct.pjs" /run /SilentMode /ForceConversion /ns /exit "/ExportLog:c:\ProgramData\Jenkins\workspace\Sandbox\TestComplete Scripted Pipeline\1580133532072.tclogx" "/ExportLog:c:\ProgramData\Jenkins\workspace\Sandbox\TestComplete Scripted Pipeline\1580133532072.htmlx" "/ErrorLog:c:\ProgramData\Jenkins\workspace\Sandbox\TestComplete Scripted Pipeline\1580133532072.txt" "/ExportLog:c:\ProgramData\Jenkins\workspace\Sandbox\TestComplete Scripted Pipeline\1580133532072.mht" /Timeout:10800 "/project:MyLovelyProduct Server" /DoNotShowLog /JenkinsTCPluginVersion:2.2"'
[TestComplete] Test runner exit code: 2.
[TestComplete] [WARNING] Error: The property checkpoint failed, because Text does not contain the substring (case-sensitive) "not important". See Details for additional information..
[TestComplete] [WARNING] Errors occurred during the test execution.
[TestComplete] Marking the build as FAILED.
[TestComplete] The test execution finished (MyLovelyProduct/MyLovelyProduct Server).

TestCompletePlugin 2.4

[TestComplete] The test execution started (MyLovelyProduct/MyLovelyProduct Stargate).
[TestComplete] Found TestComplete/TestExecute installations:
	Type: TE, Version: 14.30.3743.11, Path: "C:\Program Files (x86)\SmartBear\TestExecute 14\x64\bin\TestExecute.exe"
[TestComplete] Selected TestComplete/TestExecute installation:
	Type: TE, Version: 14.30.3743.11, Path: "C:\Program Files (x86)\SmartBear\TestExecute 14\x64\bin\TestExecute.exe"
[TestComplete] [WARNING] The node is connected via Java Web Start (JNLP). In this mode, the "Run interactive user session" property of the TestComplete Test step is ignored. TestComplete (or TestExecute) will work in the current user session.
[TestComplete] Launching the test runner.

$ "null\SessionCreator.exe" ExecuteProcess '/c:""C:\Program Files (x86)\SmartBear\TestExecute 14\x64\bin\TestExecute.exe"" ""c:\ProgramData\Jenkins\workspace\MyLovelyProduct QA\Yoda TestComplete\MyLovelyProduct.pjs"" /run /SilentMode /ForceConversion /ns /exit ""/ExportLog:c:\ProgramData\Jenkins\workspace\MyLovelyProduct QA\Yoda TestComplete\1580394292201.tclogx"" ""/ExportLog:c:\ProgramData\Jenkins\workspace\MyLovelyProduct QA\Yoda TestComplete\1580394292201.htmlx"" ""/ErrorLog:c:\ProgramData\Jenkins\workspace\MyLovelyProduct QA\Yoda TestComplete\1580394292201.txt"" ""/ExportLog:c:\ProgramData\Jenkins\workspace\MyLovelyProduct QA\Yoda TestComplete\1580394292201.mht"" /Timeout:1800 ""/project:MyLovelyProduct Stargate"" /DoNotShowLog /JenkinsTCPluginVersion:2.4'
[TestComplete] [ERROR] An exception occurred:
java.io.IOException: CreateProcess error=2, The system cannot find the file specified.
[TestComplete] Marking the build as FAILED.
[TestComplete] [WARNING] Unable to publish test results (xml data is empty).
[TestComplete] The test execution finished (MyLovelyProduct/MyLovelyProduct Stargate).

Fun thing is, in TCPlugin 2.4 the Log shows a warning that we use Java Web Start, however we disconntinued using it since the new Jenkins Server does not support Javaws with OpenJDK11.

You can even see, that the execution Line looks quite different now and it is using some "SessionCreate.exe"

 

Does someone have an idea how to get the system running again?

 

Cheers,

Constantin

  • Just a follow up - I see that you created a support ticket got a response.

     

    It is confirmed as a bug for a scenario when the master node has a Linux OS. The fix will be included in the next plugin version. 

  • sonya_m's avatar
    sonya_m
    SmartBear Alumni (Retired)

    Hi Fimbultyr , it looks like our support engineers need to look at your situation more closely. Please open a ticket with our support team.

    As soon as you get any solution, feel free to share it in this thread, thank you!

     

     

     

    • sonya_m's avatar
      sonya_m
      SmartBear Alumni (Retired)

      Just a follow up - I see that you created a support ticket got a response.

       

      It is confirmed as a bug for a scenario when the master node has a Linux OS. The fix will be included in the next plugin version.