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

Link between Jenkins and HPE ALM

XMLWordPrintable

      I use plugin Micro Focus Application Automation Tools v7.0 and try to connect to HPE ALM 12.55 with https connection. I added CA to Java cacerts file(/opt/java/openjdk/jre/lib/security) on Jenkins server. HPE Connectivity Tool(/qcbin/TDConnectivity_index.html) was installed on client.
      There isn't any error message, but authentication attempt doesn't appear on ALM admin and there isn't any notification about successful connection on Jenkins config page.

          [JENKINS-66693] Link between Jenkins and HPE ALM

          Hilda added a comment -

          Hello,

          When the authentication from Jenkins to ALM in unsuccessful there will be a message in the Console regarding the failure of the authentication:

          "Failed to login. Please contact system administrator for help.
          Description: Authentication failed. Verify your user name and password ... "

          In case of successful authentication, the plugin will start to execute the configured Test Sets from ALM.

          Regarding ALM, login authentication failures are logged in the log file (Site Administration -> Servers tab, and find the Log File Location), they are not logged in the Site Admin.

           

           

          Hilda added a comment - Hello, When the authentication from Jenkins to ALM in unsuccessful there will be a message in the Console regarding the failure of the authentication: "Failed to login. Please contact system administrator for help. Description: Authentication failed. Verify your user name and password ... " In case of successful authentication, the plugin will start to execute the configured Test Sets from ALM. Regarding ALM, login authentication failures are logged in the log file (Site Administration -> Servers tab, and find the Log File Location), they are not logged in the Site Admin.    

          Akos added a comment -

          hildaboth : "In case of successful authentication, the plugin will start to execute the configured Test Sets from ALM."
          How should I configure these Test sets in ALM?
          I can't see any authentication failures.

          Akos added a comment - hildaboth  : "In case of successful authentication, the plugin will start to execute the configured Test Sets from ALM." How should I configure these Test sets in ALM? I can't see any authentication failures.

          Hilda added a comment -

          Test Sets in ALM should contain UFT Tests, and the Test Set must be either Default or Functional type.

          Can you provide us more information about how you are using the MF Application Automation Tools plugin? Is it possible to show us the configuration of the Jenkins Job where you are using ALM, and any Console output for the job execution?

          Hilda

          Hilda added a comment - Test Sets in ALM should contain UFT Tests, and the Test Set must be either Default or Functional type. Can you provide us more information about how you are using the MF Application Automation Tools plugin? Is it possible to show us the configuration of the Jenkins Job where you are using ALM, and any Console output for the job execution? Hilda

          Rollin added a comment -

          Hi What build step were you using to execute the test set?

          Rollin added a comment - Hi What build step were you using to execute the test set?

          Akos added a comment -

          I see the following after execution is failed:
          Running as SYSTEM
          Building in workspace /var/jenkins_home/workspace/ALMTEST
          [ALMTEST] $ /var/jenkins_home/workspace/ALMTEST/HpToolsLauncher.exe -paramfile props18102021131418257.txt
          Build step 'Execute Micro Focus functional tests from Micro Focus ALM' changed build result to FAILURE

          Jenkins is installed on Ubuntu, so I am not sure why is exe file on path.

          Akos added a comment - I see the following after execution is failed: Running as SYSTEM Building in workspace /var/jenkins_home/workspace/ALMTEST [ALMTEST] $ /var/jenkins_home/workspace/ALMTEST/HpToolsLauncher.exe -paramfile props18102021131418257.txt Build step 'Execute Micro Focus functional tests from Micro Focus ALM' changed build result to FAILURE Jenkins is installed on Ubuntu, so I am not sure why is exe file on path.

          Hilda added a comment -

          The slave machine where the tests are running must be a Windows machine. UFT is not supported on Linux.

          Thank you,

          Hilda

          Hilda added a comment - The slave machine where the tests are running must be a Windows machine. UFT is not supported on Linux. Thank you, Hilda

            hildaboth Hilda
            kovacsa Akos
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: