Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-58358

Ger error: The test management module is not available in running ECU-TEST instance

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      I try to upload the testresults of ecu test to Polarion using the 
      publishTMS command. On a local jenkins installation everything works fine but on our jenkins running on a server and using a build slave I get following error:
       
      "[TT] ERROR: Failed publishing report to test management system.

      [TT] ERROR: The test management module is not available in running ECU-TEST instance! Enable it by setting the feature flag 'TEST-MANAGEMENT-SERVICE'.

      [TT] ERROR: Caught ComException: Invoke of: GetTestManagementModule Source: Description: Testmanagement is not available."

       

      where can I set the mentioned feature flag TEST-MANAGEMENT-SERVICE?

        Attachments

          Activity

          Hide
          tracetronic TraceTronic GmbH added a comment -

          Hello Arkadi Bahnmann,

          it seems to be different ECU-TEST versions between your local installation and the installation on the build slave. The feature flag didn't exist since ECU-TEST 6.6.
          Can you provide the version of the ECU-TEST instances and the use ECU-TEST-jenkins-plugin version(s).

          To set a feature flag you have to do the follwing steps:
          1. Go to your ECU-TEST Workspace.
          2. Open the workspacesettings dir or create it
          3. Open or create the file features.xml
          4a. (features.xml created)

          <?xml version="1.0" encoding="utf-8"?>
          <FEATURE-SETTINGS xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
          	<FEATURES>
          		<FEATURE xsi:type="string">TEST-MANAGEMENT-SERVICE</FEATURE>
          	</FEATURES>
          </FEATURE-SETTINGS> 

          4b. (features.xml existing)

          ... 
           <FEATURES>
            ...
            <FEATURE xsi:type="string">TEST-MANAGEMENT-SERVICE</FEATURE>
            ...
           </FEATURES>
          ...

           

          Best Regards

          Show
          tracetronic TraceTronic GmbH added a comment - Hello Arkadi Bahnmann , it seems to be different ECU-TEST versions between your local installation and the installation on the build slave. The feature flag didn't exist since ECU-TEST 6.6. Can you provide the version of the ECU-TEST instances and the use ECU-TEST-jenkins-plugin version(s). To set a feature flag you have to do the follwing steps: 1. Go to your ECU-TEST Workspace. 2. Open the workspacesettings dir or create it 3. Open or create the file features.xml 4a. ( features.xml created) <?xml version= "1.0" encoding= "utf-8" ?> <FEATURE-SETTINGS xmlns:xsi= "http: //www.w3.org/2001/XMLSchema-instance" > <FEATURES> <FEATURE xsi:type= "string" >TEST-MANAGEMENT-SERVICE</FEATURE> </FEATURES> </FEATURE-SETTINGS> 4b. ( features.xml existing) ... <FEATURES> ... <FEATURE xsi:type= "string" >TEST-MANAGEMENT-SERVICE</FEATURE> ... </FEATURES> ...   Best Regards
          Hide
          b_arkadi Arkadi Bahnmann added a comment -

          The ECU Test version on the local machine and the server are both 8.0.

          On the server the plug-in version 2.8 was used and on the local jenkins installation 2.9 was used.

          Now both systems were updated to version 2.10. But to test if the failure is gone with the newest version, a have to wait until the jenkins on the server will be restarted the next time. Unfortunatly this will take some time.

          Show
          b_arkadi Arkadi Bahnmann added a comment - The ECU Test version on the local machine and the server are both 8.0. On the server the plug-in version 2.8 was used and on the local jenkins installation 2.9 was used. Now both systems were updated to version 2.10. But to test if the failure is gone with the newest version, a have to wait until the jenkins on the server will be restarted the next time. Unfortunatly this will take some time.
          Hide
          tracetronic TraceTronic GmbH added a comment -

          @Arkadi Bahnmann:
          Are you sure that there is no other ECU-TEST version installed and configured on the jenkins slave. The output doesn't look like the output of ECU-TEST 8.0.

          The differences between the plugin versions of 2.8/2.9/2.10 shouldn't have any impact on your problem. Can you please open a support ticket at support@tracetronic.de and provide ECU-TEST and jenkins logfiles from the concerned test environment?

          Thanks and Best Regards 

          Show
          tracetronic TraceTronic GmbH added a comment - @ Arkadi Bahnmann : Are you sure that there is no other ECU-TEST version installed and configured on the jenkins slave. The output doesn't look like the output of ECU-TEST 8.0. The differences between the plugin versions of 2.8/2.9/2.10 shouldn't have any impact on your problem. Can you please open a support ticket at support@tracetronic.de and provide ECU-TEST and jenkins logfiles from the concerned test environment? Thanks and Best Regards 
          Hide
          b_arkadi Arkadi Bahnmann added a comment -

          Yes I'm sure..This is the first time we use ECU-Test on our jenkins server and only version 8.0 was installed. Also in the screenshot below you can see, that the plug-in starts ECU Test 8.0

          Also like you metioned before, I created a workspacesettings folder with the features.xml file, but this does not solve the problem.

          This seems to be a very weird behaviour.

          I hope that tomorrow morning our jenkins server will be restarted and I can check if this failure is gone with version 2.10.

          If not I will contact the support team.

          Show
          b_arkadi Arkadi Bahnmann added a comment - Yes I'm sure..This is the first time we use ECU-Test on our jenkins server and only version 8.0 was installed. Also in the screenshot below you can see, that the plug-in starts ECU Test 8.0 Also like you metioned before, I created a workspacesettings folder with the features.xml file, but this does not solve the problem. This seems to be a very weird behaviour. I hope that tomorrow morning our jenkins server will be restarted and I can check if this failure is gone with version 2.10. If not I will contact the support team.
          Hide
          b_arkadi Arkadi Bahnmann added a comment -

          Here is another screenshot from the toolsetting section of the published testresult in jenkins

          Show
          b_arkadi Arkadi Bahnmann added a comment - Here is another screenshot from the toolsetting section of the published testresult in jenkins
          Hide
          b_arkadi Arkadi Bahnmann added a comment -

          Updating the plug-in to version 2.10 also did not solve the problem.

          Show
          b_arkadi Arkadi Bahnmann added a comment - Updating the plug-in to version 2.10 also did not solve the problem.
          Hide
          b_arkadi Arkadi Bahnmann added a comment -

          We finally solved the problem. It was a problem with the path variable to the java installation on the jenkins server.

          By running the testmanagement export using the ECU Test exe on the jenkins server, ECU-Test raised a error message which was very helpful.

          The error message from the plugin on the other hand was verry confusing and had nothing to do with the actual failure. 

          Show
          b_arkadi Arkadi Bahnmann added a comment - We finally solved the problem. It was a problem with the path variable to the java installation on the jenkins server. By running the testmanagement export using the ECU Test exe on the jenkins server, ECU-Test raised a error message which was very helpful. The error message from the plugin on the other hand was verry confusing and had nothing to do with the actual failure. 
          Hide
          tracetronic TraceTronic GmbH added a comment -

          @Arkadi Bahnmann
          I opened a ticket because of the faulty error messages on [Github|https://github.com/jenkinsci/ecutest-plugin/issues/70]

          Show
          tracetronic TraceTronic GmbH added a comment - @ Arkadi Bahnmann I opened a ticket because of the faulty error messages on [Github| https://github.com/jenkinsci/ecutest-plugin/issues/70 ]
          Hide
          b_arkadi Arkadi Bahnmann added a comment -

          Ok. Thank you

          Show
          b_arkadi Arkadi Bahnmann added a comment - Ok. Thank you

            People

            Assignee:
            tracetronic TraceTronic GmbH
            Reporter:
            b_arkadi Arkadi Bahnmann
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: