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

Upload test result to ALM failed to parse file with Java 11

XMLWordPrintable

      Hello,
      the ALM Plugin should support Java 8 and above, but after I switch to Java 11 the JUnit result file can not parsed by the plugin.

      15:33:37 [Checks API] No suitable checks publisher found.
15:33:37 INFO: 'Upload test result to ALM' Post Build Step is being invoked by q-was-alm.
15:33:37 INFO: 1 test result file found.
15:33:37 INFO: Start to upload /usd/as97385a/work/jenkins/jobs/Introscope/jobs/agent_java-alm/builds/5/results_junit.xml
15:33:37 INFO: Start to parse file: /usd/as97385a/work/jenkins/jobs/Introscope/jobs/agent_java-alm/builds/5/results_junit.xml
15:33:37 Failed to parse file with: com.microfocus.application.automation.tools.results.parser.jenkinsjunit.JenkinsJUnitReportParserImpl
15:33:37 Failed to parse file with: com.microfocus.application.automation.tools.results.parser.mavensurefire.MavenSureFireReportParserImpl
15:33:37 Failed to parse file with: com.microfocus.application.automation.tools.results.parser.testngxml.TestNGXmlReportParserImpl
15:33:38 Failed to parse file with: com.microfocus.application.automation.tools.results.parser.nunit3.NUnit3ReportParserImpl
15:33:38 Failed to parse file with: com.microfocus.application.automation.tools.results.parser.nunit.NUnitReportParserImpl
15:33:38 Failed to parse file with: com.microfocus.application.automation.tools.results.parser.antjunit.AntJUnitReportParserImpl
15:33:38 ERR: There's exception while uploading /usd/as97385a/work/jenkins/jobs/Introscope/jobs/agent_java-alm/builds/5/results_junit.xml. Failed to parse file: /usd/as97385a/work/jenkins/jobs/Introscope/jobs/agent_java-alm/builds/5/results_junit.xml
15:33:38 INFO: 'Upload test result to ALM' Completed.
15:33:38 Build step 'Upload test result to ALM' changed build result to UNSTABLE
15:33:38 [lockable-resources] released lock on [INTROSCOPE_ALM, INTROSCOPE_JAVA]
15:33:38 Finished: UNSTABLE

      Based on Java 8 the JUnit result file was read by the Antjunit report parser.

      Any idea what is going wrong.

      I do all tests based on Jenkins 2.319.2, 2.319.3 and 2.332.2
      and Micro Focus Application Automation Tools 7.2 and 7.3

      The import works well in a java version "1.8.0_321" environment but
      does not with java version "11.0.14" 2022-01-18 LTS

      With regards,
      Lutz

        1. image-2022-07-29-10-00-43-795.png
          image-2022-07-29-10-00-43-795.png
          117 kB

          [JENKINS-68228] Upload test result to ALM failed to parse file with Java 11

          Hilda added a comment -

          Hello,

          Currently our plugin is working as expected with Java 8.

          We are planning to upgrade to Java 11 and optimize it in our next release, version 7.4, which will be in the end of June.

          We will handle this issue as well.

          Thank you,

          Hilda 

          Hilda added a comment - Hello, Currently our plugin is working as expected with Java 8. We are planning to upgrade to Java 11 and optimize it in our next release, version 7.4, which will be in the end of June. We will handle this issue as well. Thank you, Hilda 

          Lutz Mader added a comment - - edited

          Hello Hilda,
          you are right, the plugin is working as expected with Java 8, unfortunately Jenkins will move to Java 11.

          Nice to know someone have a look to the problem, thanks for all information. I will switch to version 7.4 in June.

          With regards,
          Lutz

          Lutz Mader added a comment - - edited Hello Hilda, you are right, the plugin is working as expected with Java 8, unfortunately Jenkins will move to Java 11. Nice to know someone have a look to the problem, thanks for all information. I will switch to version 7.4 in June. With regards, Lutz

          Basil Crow added a comment -

          Adding the JAXB plugin as a plugin-to-plugin dependency as in jenkinsci/hpe-application-automation-tools-plugin#493 should be a good place to start. Once that is done, the calls to javax.xml.bind.JAXBContext.newInstance in com.hp.alm.ali.hudson.JAXBApi.marshall (is the source code to this class on GitHub?) need to be wrapped in the correct context class loader as in jenkinsci/xcode-plugin#113.

          Basil Crow added a comment - Adding the JAXB plugin as a plugin-to-plugin dependency as in jenkinsci/hpe-application-automation-tools-plugin#493 should be a good place to start. Once that is done, the calls to javax.xml.bind.JAXBContext.newInstance in com.hp.alm.ali.hudson.JAXBApi.marshall (is the source code to this class on GitHub?) need to be wrapped in the correct context class loader as in jenkinsci/xcode-plugin#113 .

          Dorin Bogdan added a comment -

          Hi basil ,

          We reproduced the issue using a recent build.
          For the fix I followed your suggestion from jenkinsci/xcode-plugin#113 and applied it on several classes.
          If you have any observation, please let me know.
          For example, do you suspect any negative effect on the static methods affected in this PR?

          Thank you.

          Dorin Bogdan added a comment - Hi basil , We reproduced the issue using a recent build. For the fix I followed your suggestion from  jenkinsci/xcode-plugin#113  and applied it on several classes. If you have any observation, please let me know. For example, do you suspect any negative effect on the static methods affected in this PR ? Thank you.

          Basil Crow added a comment -

          Great! BTW this document explains the gory details about why this is necessary in the Jenkins plugin class loading system. In the future I hope to provide a utility class in Jenkins core that will make it easier to set the context class loader, but for the time being this is the recommended practice. Thanks!

          Basil Crow added a comment - Great! BTW this document explains the gory details about why this is necessary in the Jenkins plugin class loading system. In the future I hope to provide a utility class in Jenkins core that will make it easier to set the context class loader, but for the time being this is the recommended practice. Thanks!

          Hilda added a comment -

          Hello,

          The new version for "Micro Focus Application Automation Tools" version 7.4 is available with the fix for the parsing issue.

          Thank you,

          Hilda Both

          Hilda added a comment - Hello, The new version for "Micro Focus Application Automation Tools" version 7.4 is available with the fix for the parsing issue. Thank you, Hilda Both

          Lutz Mader added a comment - - edited

          Hello,
          I am on Jenkins 2.346.1 with Java 11.0.15.1 2022-04-22 LTS

          After I update the "Micro Focus Application Automation Tools" from 7.3 to 7.4.
          In "Pipeline", "Definition Pipeline script" the "Script" will not shown (the field is empty),
          but the script is still available in the "config.xml" file of the job. I can start the jobs.
          After I go back to 7.3 the "Script" will shown again!

          I will try to find some useful error messages, but I have not found anything, sorry.

          A warning only,
          Lutz

          Lutz Mader added a comment - - edited Hello, I am on Jenkins 2.346.1 with Java 11.0.15.1 2022-04-22 LTS After I update the "Micro Focus Application Automation Tools" from 7.3 to 7.4. In "Pipeline", "Definition Pipeline script" the "Script" will not shown (the field is empty), but the script is still available in the "config.xml" file of the job. I can start the jobs. After I go back to 7.3 the "Script" will shown again! I will try to find some useful error messages, but I have not found anything, sorry. A warning only, Lutz

          Lutz Mader added a comment - - edited

          Hello,
          I am on Jenkins 2.346.1 with Java 11.0.15.1 2022-04-22 LTS

          After I update the "Micro Focus Application Automation Tools" from 7.3 to 7.4.
          In "Pipeline", "Definition Pipeline script" the "Script" will not shown (the field is empty),
          but the script is still available in the "config.xml" file of the job.

          After I go back to 7.3 the "Script" will shown again!

          In a clean installed Jenkins environment I updated the "Pipeline Definition", but after reopening the Job again, the defaults are shown. But, the changes are written to the "jenkins.xml" file. Jenkins can not read the of the "Pipeline" settings from the file, I think.
          After I uninstall the plugin, every things work as expected.

          Any suggestion?
          Sorry,
          Lutz

          Lutz Mader added a comment - - edited Hello, I am on Jenkins 2.346.1 with Java 11.0.15.1 2022-04-22 LTS After I update the "Micro Focus Application Automation Tools" from 7.3 to 7.4. In "Pipeline", "Definition Pipeline script" the "Script" will not shown (the field is empty), but the script is still available in the "config.xml" file of the job. After I go back to 7.3 the "Script" will shown again! In a clean installed Jenkins environment I updated the "Pipeline Definition", but after reopening the Job again, the defaults are shown. But, the changes are written to the "jenkins.xml" file. Jenkins can not read the of the "Pipeline" settings from the file, I think. After I uninstall the plugin, every things work as expected. Any suggestion? Sorry, Lutz

          Hilda added a comment -

          Hello,

          Yes, unfortunately this is a limitation for now in the plugin version 7.4., but the functionality of the pipeline execution is not affected, since, as you also mentioned, the config.xml file contains the script. 

          We are aware of the problem and we are already working on a beta version to fix this issue.

          Once it's ready I will upload the beta version.

          Thank you for your understanding,

          Hilda Both

          Hilda added a comment - Hello, Yes, unfortunately this is a limitation for now in the plugin version 7.4., but the functionality of the pipeline execution is not affected, since, as you also mentioned, the config.xml file contains the script.  We are aware of the problem and we are already working on a beta version to fix this issue. Once it's ready I will upload the beta version. Thank you for your understanding, Hilda Both

          Lutz Mader added a comment -

          Hello Hilda Both,
          thanks for all your help.
          I/we downgrade to the version 7.3 plugin and Java 1.8 again.

          You are right, the pipelines are stil working, but the definitions/configuration is not shown for the pipeline. It was a bit strange, but we lost no data.

          Let me know if I/we can do some additional tests or give you some help.

          Thanks for all help,
          have a nice weekend,
          Lutz

          Lutz Mader added a comment - Hello Hilda Both, thanks for all your help. I/we downgrade to the version 7.3 plugin and Java 1.8 again. You are right, the pipelines are stil working, but the definitions/configuration is not shown for the pipeline. It was a bit strange, but we lost no data. Let me know if I/we can do some additional tests or give you some help. Thanks for all help, have a nice weekend, Lutz

          Hilda added a comment -

          Hello lutzmad 

          Thank you for your help.

          This is the link to the new beta version, which contains the fix. 

          https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/hp-application-automation-tools-plugin/7.4.1-beta/

          For any issues, please feel free to contact us.

          Thank you,

          Hilda

          Hilda added a comment - Hello lutzmad   Thank you for your help. This is the link to the new beta version, which contains the fix.  https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/hp-application-automation-tools-plugin/7.4.1-beta/ For any issues, please feel free to contact us. Thank you, Hilda

          Lutz Mader added a comment - - edited

          Hello all folks,
          thanks for the fast test/fixed plugin. From my point of view I can not find glitches in a Java 8 and Java 11 environment yet.
          The problems based on the 7.4 plugin disappeared, the pipeline settings are accessible after applying the plugin.

          Nice, I switched to the 7.4.1 plugin (I know this is a test version only).

          THANKS,
          Lutz

          A sipped from the log:
          The messages "Failed to parse file with:" are normal, the plugin try to find the right filter to upload the data. It is a normal JUnit file, but the filter decide it does not fit to "JenkinsJUnitReportParserImpl". But the upload work well, I find some data in the QC.

          17:53:31 Recording test results
17:53:31 [Checks API] No suitable checks publisher found.
17:53:31 INFO: 'Upload test result to ALM' Post Build Step is being invoked by q-was-alm.
17:53:31 INFO: 1 test result file found.
17:53:31 INFO: Start to upload /usd/as98765a/work/jenkins/jobs/Introscope/jobs/agent_java-alm/builds/13/results_junit.xml
17:53:31 INFO: Start to parse file: /usd/as98765a/work/jenkins/jobs/Introscope/jobs/agent_java-alm/builds/13/results_junit.xml
17:53:31 Failed to parse file with: com.microfocus.application.automation.tools.results.parser.jenkinsjunit.JenkinsJUnitReportParserImpl
17:53:31 Failed to parse file with: com.microfocus.application.automation.tools.results.parser.mavensurefire.MavenSureFireReportParserImpl
17:53:31 Failed to parse file with: com.microfocus.application.automation.tools.results.parser.testngxml.TestNGXmlReportParserImpl
17:53:32 Failed to parse file with: com.microfocus.application.automation.tools.results.parser.nunit3.NUnit3ReportParserImpl
17:53:32 Failed to parse file with: com.microfocus.application.automation.tools.results.parser.nunit.NUnitReportParserImpl
17:53:32 INFO: parse resut file succeed.
17:53:32 INFO: Start to login to ALM Server.
17:53:32 Start login to ALM server...
17:53:32 User q-was-alm unauthorized.
17:53:32 Got authenticate point:https://qualitycenter.intern:0/qcbin/authentication-point/authenticate
17:53:32 Authenticate point schema or port is different with server's. Please check with ALM site admin.
17:53:32 Try to authenticate through: https://qualitycenter.intern/qcbin/authentication-point/authenticate
17:53:32 Logged in successfully to ALM Server https://qualitycenter.intern/qcbin/ using q-was-alm
17:53:32 Creating session...
17:53:32 Session created.
17:53:32 INFO: Checking test folder...
17:53:32 INFO: Checking testset folder...
17:53:32 INFO: Uploading ALM Entities...
17:53:34 INFO: Uploaded /usd/as98765a/work/jenkins/jobs/Introscope/jobs/agent_java-alm/builds/13/results_junit.xml.
17:53:34 INFO: 'Upload test result to ALM' Completed.
17:53:34 [lockable-resources] released lock on [INTROSCOPE_ALM, INTROSCOPE_JAVA]
17:53:34 Finished: SUCCESS

          Lutz Mader added a comment - - edited Hello all folks, thanks for the fast test/fixed plugin. From my point of view I can not find glitches in a Java 8 and Java 11 environment yet. The problems based on the 7.4 plugin disappeared, the pipeline settings are accessible after applying the plugin. Nice, I switched to the 7.4.1 plugin (I know this is a test version only). THANKS, Lutz A sipped from the log: The messages "Failed to parse file with:" are normal, the plugin try to find the right filter to upload the data. It is a normal JUnit file, but the filter decide it does not fit to "JenkinsJUnitReportParserImpl". But the upload work well, I find some data in the QC. 17:53:31 Recording test results 17:53:31 [Checks API] No suitable checks publisher found. 17:53:31 INFO: 'Upload test result to ALM' Post Build Step is being invoked by q-was-alm. 17:53:31 INFO: 1 test result file found. 17:53:31 INFO: Start to upload /usd/as98765a/work/jenkins/jobs/Introscope/jobs/agent_java-alm/builds/13/results_junit.xml 17:53:31 INFO: Start to parse file: /usd/as98765a/work/jenkins/jobs/Introscope/jobs/agent_java-alm/builds/13/results_junit.xml 17:53:31 Failed to parse file with: com.microfocus.application.automation.tools.results.parser.jenkinsjunit.JenkinsJUnitReportParserImpl 17:53:31 Failed to parse file with: com.microfocus.application.automation.tools.results.parser.mavensurefire.MavenSureFireReportParserImpl 17:53:31 Failed to parse file with: com.microfocus.application.automation.tools.results.parser.testngxml.TestNGXmlReportParserImpl 17:53:32 Failed to parse file with: com.microfocus.application.automation.tools.results.parser.nunit3.NUnit3ReportParserImpl 17:53:32 Failed to parse file with: com.microfocus.application.automation.tools.results.parser.nunit.NUnitReportParserImpl 17:53:32 INFO: parse resut file succeed. 17:53:32 INFO: Start to login to ALM Server. 17:53:32 Start login to ALM server... 17:53:32 User q-was-alm unauthorized. 17:53:32 Got authenticate point:https://qualitycenter.intern:0/qcbin/authentication-point/authenticate 17:53:32 Authenticate point schema or port is different with server's. Please check with ALM site admin. 17:53:32 Try to authenticate through: https://qualitycenter.intern/qcbin/authentication-point/authenticate 17:53:32 Logged in successfully to ALM Server https://qualitycenter.intern/qcbin/ using q-was-alm 17:53:32 Creating session... 17:53:32 Session created. 17:53:32 INFO: Checking test folder... 17:53:32 INFO: Checking testset folder... 17:53:32 INFO: Uploading ALM Entities... 17:53:34 INFO: Uploaded /usd/as98765a/work/jenkins/jobs/Introscope/jobs/agent_java-alm/builds/13/results_junit.xml. 17:53:34 INFO: 'Upload test result to ALM' Completed. 17:53:34 [lockable-resources] released lock on [INTROSCOPE_ALM, INTROSCOPE_JAVA] 17:53:34 Finished: SUCCESS

          Andreas Mandel added a comment -

          Thanks for the fix. I wonder if the release of 7.4.1 is blocked somehow. The update center still lists the broken 7.4 and every user updating will run into this critical issue.

          Andreas Mandel added a comment - Thanks for the fix. I wonder if the release of 7.4.1 is blocked somehow. The update center still lists the broken 7.4 and every user updating will run into this critical issue.

          Basil Crow added a comment -

          The release of https://plugins.jenkins.io/hp-application-automation-tools-plugin/ 7.4.1 apparently did not succeed as the plugin site is listing 7.4. CC hildaboth dbogdan7

          Basil Crow added a comment - The release of https://plugins.jenkins.io/hp-application-automation-tools-plugin/ 7.4.1 apparently did not succeed as the plugin site is listing 7.4. CC hildaboth dbogdan7

          Dorin Bogdan added a comment - - edited

          Hi andreasmandel,

          I'm not sure if / when the plugin site will be updated with beta versions.

          I just forwarded the question to the plugin owner and she told that it was expected to be automatically updated...

          Currently, the most recent is 7.4.2-beta, and the full list is in the Jenkins repository:

          https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/hp-application-automation-tools-plugin/

          Thank you for understanding.

          CC plescaevelyn 

          Dorin Bogdan added a comment - - edited Hi andreasmandel , I'm not sure if / when the plugin site will be updated with beta versions. I just forwarded the question to the plugin owner and she told that it was expected to be automatically updated... Currently, the most recent is 7.4.2-beta , and the full list is in the Jenkins repository: https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/hp-application-automation-tools-plugin/ Thank you for understanding. CC plescaevelyn  

          Basil Crow added a comment -

          Ah I see, only a beta version was published. Here is the documentation for experimental plugin releases:

          https://www.jenkins.io/doc/developer/publishing/releasing-experimental-updates/

          Note that very few Jenkins users (a minuscule number) use the Experimental Update Center. The vast majority of Jenkins users will be using the standard update center, which is currently publishing the broken 7.4 version. So I would recommend a non-beta version be released for the benefit of those users.

          Basil Crow added a comment - Ah I see, only a beta version was published. Here is the documentation for experimental plugin releases: https://www.jenkins.io/doc/developer/publishing/releasing-experimental-updates/ Note that very few Jenkins users (a minuscule number) use the Experimental Update Center. The vast majority of Jenkins users will be using the standard update center, which is currently publishing the broken 7.4 version. So I would recommend a non-beta version be released for the benefit of those users.

          Lutz Mader added a comment - - edited

          Hello,
          I upgraded to the new 7.4.2-beta. Seems to me working well, therefore I use the 7.4.2-beta in the production Jenkins (Jenkins 2.346.2 and Java 11.0.15.1+2-LTS-10) again.

          Nice, thanks for all help,
          Lutz

          Appendage:

          09:41:32 [Checks API] No suitable checks publisher found.
09:41:32 INFO: 'Upload test result to ALM' Post Build Step is being invoked by q-was-alm.
09:41:32 INFO: 1 test result file found.
09:41:32 INFO: Start to upload /usd/as98765a/work/jenkins/jobs/Introscope/jobs/agent_java-alm/builds/14/results_junit.xml
09:41:32 INFO: Start to parse file: /usd/as98765a/work/jenkins/jobs/Introscope/jobs/agent_java-alm/builds/14/results_junit.xml
09:41:32 Failed to parse file with: com.microfocus.application.automation.tools.results.parser.jenkinsjunit.JenkinsJUnitReportParserImpl
09:41:32 Failed to parse file with: com.microfocus.application.automation.tools.results.parser.mavensurefire.MavenSureFireReportParserImpl
09:41:32 Failed to parse file with: com.microfocus.application.automation.tools.results.parser.testngxml.TestNGXmlReportParserImpl
09:41:33 Failed to parse file with: com.microfocus.application.automation.tools.results.parser.nunit3.NUnit3ReportParserImpl
09:41:33 Failed to parse file with: com.microfocus.application.automation.tools.results.parser.nunit.NUnitReportParserImpl
09:41:33 INFO: parse resut file succeed.
09:41:33 INFO: Start to login to ALM Server.
09:41:33 Start login to ALM server...
09:41:33 User q-was-alm unauthorized.
09:41:33 Got authenticate point:https://qualitycenter.intern:0/qcbin/authentication-point/authenticate
09:41:33 Authenticate point schema or port is different with server's. Please check with ALM site admin.
09:41:33 Try to authenticate through: https://qualitycenter.intern/qcbin/authentication-point/authenticate
09:41:33 Logged in successfully to ALM Server https://qualitycenter.intern/qcbin/ using q-was-alm
09:41:33 Creating session...
09:41:33 Session created.
09:41:33 INFO: Checking test folder...
09:41:33 INFO: Checking testset folder...
09:41:33 INFO: Uploading ALM Entities...
09:41:36 INFO: Uploaded /usd/as98765a/work/jenkins/jobs/Introscope/jobs/agent_java-alm/builds/14/results_junit.xml.
09:41:36 INFO: 'Upload test result to ALM' Completed.
09:41:36 [lockable-resources] released lock on [INTROSCOPE_ALM, INTROSCOPE_JAVA]
09:41:36 Finished: SUCCESS

          Lutz Mader added a comment - - edited Hello, I upgraded to the new 7.4.2-beta. Seems to me working well, therefore I use the 7.4.2-beta in the production Jenkins (Jenkins 2.346.2 and Java 11.0.15.1+2-LTS-10) again. Nice, thanks for all help, Lutz Appendage: 09:41:32 [Checks API] No suitable checks publisher found. 09:41:32 INFO: 'Upload test result to ALM' Post Build Step is being invoked by q-was-alm. 09:41:32 INFO: 1 test result file found. 09:41:32 INFO: Start to upload /usd/as98765a/work/jenkins/jobs/Introscope/jobs/agent_java-alm/builds/14/results_junit.xml 09:41:32 INFO: Start to parse file: /usd/as98765a/work/jenkins/jobs/Introscope/jobs/agent_java-alm/builds/14/results_junit.xml 09:41:32 Failed to parse file with: com.microfocus.application.automation.tools.results.parser.jenkinsjunit.JenkinsJUnitReportParserImpl 09:41:32 Failed to parse file with: com.microfocus.application.automation.tools.results.parser.mavensurefire.MavenSureFireReportParserImpl 09:41:32 Failed to parse file with: com.microfocus.application.automation.tools.results.parser.testngxml.TestNGXmlReportParserImpl 09:41:33 Failed to parse file with: com.microfocus.application.automation.tools.results.parser.nunit3.NUnit3ReportParserImpl 09:41:33 Failed to parse file with: com.microfocus.application.automation.tools.results.parser.nunit.NUnitReportParserImpl 09:41:33 INFO: parse resut file succeed. 09:41:33 INFO: Start to login to ALM Server. 09:41:33 Start login to ALM server... 09:41:33 User q-was-alm unauthorized. 09:41:33 Got authenticate point:https://qualitycenter.intern:0/qcbin/authentication-point/authenticate 09:41:33 Authenticate point schema or port is different with server's. Please check with ALM site admin. 09:41:33 Try to authenticate through: https://qualitycenter.intern/qcbin/authentication-point/authenticate 09:41:33 Logged in successfully to ALM Server https://qualitycenter.intern/qcbin/ using q-was-alm 09:41:33 Creating session... 09:41:33 Session created. 09:41:33 INFO: Checking test folder... 09:41:33 INFO: Checking testset folder... 09:41:33 INFO: Uploading ALM Entities... 09:41:36 INFO: Uploaded /usd/as98765a/work/jenkins/jobs/Introscope/jobs/agent_java-alm/builds/14/results_junit.xml. 09:41:36 INFO: 'Upload test result to ALM' Completed. 09:41:36 [lockable-resources] released lock on [INTROSCOPE_ALM, INTROSCOPE_JAVA] 09:41:36 Finished: SUCCESS

          Evelyn Plesca added a comment - - edited

          Hello,

          I have released version 7.4.3 as an official release.
          I am waiting for the plugin site (https://plugins.jenkins.io/hp-application-automation-tools-plugin/#releases) to be automatically updated in a few hours.

          Until then, you can find the release here:
          https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/hp-application-automation-tools-plugin/

          Evelyn Plesca added a comment - - edited Hello, I have released version 7.4.3 as an official release. I am waiting for the plugin site ( https://plugins.jenkins.io/hp-application-automation-tools-plugin/#releases) to be automatically updated in a few hours. Until then, you can find the release here: https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/hp-application-automation-tools-plugin/

          Lutz Mader added a comment -

          Hello Evelyn Plesca,
          nice to know.
          > I have released version 7.4.3 as an official release.

          I will switch to the new 7.4.3 plugin tomorrow,
          thanks for all help.
          Lutz

          Lutz Mader added a comment - Hello Evelyn Plesca, nice to know. > I have released version 7.4.3 as an official release. I will switch to the new 7.4.3 plugin tomorrow, thanks for all help. Lutz

          Dorin Bogdan added a comment -

          The site was updated https://plugins.jenkins.io/hp-application-automation-tools-plugin/#releases.

          If you still don't see 7.4.3 then please clear the browser cache and reload.

          Dorin Bogdan added a comment - The site was updated https://plugins.jenkins.io/hp-application-automation-tools-plugin/#releases. If you still don't see 7.4.3 then please clear the browser cache and reload.

          Lutz Mader added a comment -

          Hello,
          thanks for your help, I/we migrated to the new version.

          Micro Focus Application Automation Tools Version 7.4.3
          Jenkins 2.346.2
          Java 11.0.15.1+2-LTS-10

          It seems to me working well,
          have a nice weekend,
          Lutz

          Lutz Mader added a comment - Hello, thanks for your help, I/we migrated to the new version. Micro Focus Application Automation Tools Version 7.4.3 Jenkins 2.346.2 Java 11.0.15.1+2-LTS-10 It seems to me working well, have a nice weekend, Lutz

          Lutz Mader added a comment - - edited

          Hello,
          the new version seems to working well,
          I close the ticket.

          Thanks for all help,
          have a nice weekend,
          Lutz

          Lutz Mader added a comment - - edited Hello, the new version seems to working well, I close the ticket. Thanks for all help, have a nice weekend, Lutz

            hildaboth Hilda
            lutzmad Lutz Mader
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: