-
Bug
-
Resolution: Fixed
-
Major
-
HP Application Automation Tools Plugin Version 5.3
Jenkins version 2.70
When trying to connect to an SaaS HP ALM server from Jenkins on a RHEL7 box via a Windows Slave, the connection fails and the log contains the following info:
"
13:32:35 Started by user Josh Privett
13:32:35 Building remotely on alm_connection in workspace C:\Jenkins\workspace\Run_HP_ALM_Tests
13:32:35 Start login to ALM server.
13:32:36 Login to ALM Server at https://xxxxxxxxxxx/qcbin/ failed. Status Code: 302
13:32:36 Empty Results
13:32:36 Result Status: UNSTABLE
13:32:36 Build step 'Execute HPE tests using HPE ALM Lab Management' changed build result to UNSTABLE
13:32:37 Finished: UNSTABLE
"
We found that this was an issue in the past with https but it had allegedly been fixed in 5.2. We have confirmed that the credentials are correct for logging in. What are we doing incorrectly?
[JENKINS-48727] Jenkins HP Plugin Unable to Connect to SaaS ALM Server
Marlene Macdonald
added a comment - We are also experiencing this issue with version 5.3 of the plugin. Version 5.2 is connecting without an issue.
Marlene Macdonald
added a comment - We are also experiencing this issue with version 5.3 of the plugin. Version 5.2 is connecting without an issue. 
Josh Privett
added a comment - I can confirm thanks to Marlene that reverting to 5.2 solved the problem for us as well, we were running 5.3. It would be nice to not have to worry about the version though!
Josh Privett
added a comment - I can confirm thanks to Marlene that reverting to 5.2 solved the problem for us as well, we were running 5.3. It would be nice to not have to worry about the version though! 
Hello,
We have the same problem. Is the problem solved only for "HP Performance Center" only as there is a check box to "Use HTTPS Protocol" there?
Jenkins v2.101 and HPE Application Automation Tools v5.3
We are using "Upload test result to ALM" post-build action. Error message is:
Login to ALM Server at https://****/qcbin/ failed. Status Code: 302