-
Bug
-
Resolution: Not A Defect
-
Major
-
org.jenkins-ci.main:jenkins-war:2.60.3
java.runtime.name Java(TM) SE Runtime Environment
java.runtime.version 1.8.0_66-b18
os.arch x86
os.name Windows Server 2012 R2
os.version 6.3
Proxy information has been entered via: Manage Jenkins -> Manage Plugins -> Advanced & also as arguments in the Jenkins.xml file.
org.jenkins-ci.main:jenkins-war:2.60.3 java.runtime.name Java(TM) SE Runtime Environment java.runtime.version 1.8.0_66-b18 os.arch x86 os.name Windows Server 2012 R2 os.version 6.3 Proxy information has been entered via: Manage Jenkins -> Manage Plugins -> Advanced & also as arguments in the Jenkins.xml file.
Proxy information has been entered via: Manage Jenkins -> Manage Plugins -> Advanced & also as arguments in the Jenkins.xml file.
When configuring the ALM Server connection in Manage Jenkins -> Configure System -> Application Lifecycle Management, the connection is fine. When testing the connection to the ALM server in the proxy settings (Manage Jenkins -> Manage Plugins -> Advanced), a success message is returned.
However the item (job) created experiences a connection failure. The item is configured to Execute HPE functional tests from HPE ALM. The error produced is as follows:
Server has been disconnected while performing GetServerSettings action
Error: "ALM server
url goes here
unreachable, check that server Url is correct"
Build step 'Execute HPE functional tests from HPE ALM' changed build result to FAILURE
Note that I have tried to install Jenkins outside of our network with a direct connection to the internet and I did not experience the issue, therefore I believe the proxy to be the issue.
[JENKINS-46473] Error when connecting to ALM using HPE Application Automation Tools Plugin
Marlene Macdonald
added a comment - As I was not using Lab Management I did not have the option to set the proxy settings in the build step.
I switched to the Execute HP tests using HP ALM Lab Management option as suggested and set the proxy & all information there and with some additional setups in ALM I am now able to run my automated tests. Thank you for your help!
Marlene Macdonald
added a comment - As I was not using Lab Management I did not have the option to set the proxy settings in the build step.
I switched to the Execute HP tests using HP ALM Lab Management option as suggested and set the proxy & all information there and with some additional setups in ALM I am now able to run my automated tests. Thank you for your help!
Prakash AM
added a comment - marlene_macdonald Can you please share the steps how did you fix this issue? I am facing the same issue when connecting to ALM from Jenkin.
Prakash AM
added a comment - marlene_macdonald Can you please share the steps how did you fix this issue? I am facing the same issue when connecting to ALM from Jenkin. Marlene Macdonald
added a comment - Note that only v5.2 is currently supporting connecting to ALM from Jenkins when using a proxy. The current version (v5.3) is not working. Have you tried with v5.2?
Marlene Macdonald
added a comment - Note that only v5.2 is currently supporting connecting to ALM from Jenkins when using a proxy. The current version (v5.3) is not working. Have you tried with v5.2? Prakash AM
added a comment - marlene_macdonald Yes, I downgraded to 5.2 and tested it out as well. But, still I am getting the same error as you mentioned here. Can you please share the steps you tried here(like updating proxy(please share details), updateing ALM).
Prakash AM
added a comment - marlene_macdonald Yes, I downgraded to 5.2 and tested it out as well. But, still I am getting the same error as you mentioned here. Can you please share the steps you tried here(like updating proxy(please share details), updateing ALM).
Marlene Macdonald
added a comment - 1) On Jenkins -> configuration: enter the name and URL of the ALM server under Application Lifecycle Management/ALM server
2) On Jenkins -> Plugin Manager -> Advanced: enter proxy server and port, plus optionally user/password if needed (if your proxy requires authentication) under HTTP Proxy Configuration
3) Create Item(job), Configure Build step as Execute HPE tests using HPE ALM Lab Management. Select ALM Server. Enter ALM Credentials. (Use Add button to setup first time. This is the user/password that connects to ALM) Enter Domain. Check the box "Use proxy settings". Enter your proxy address and port, x.x.x.x:80. Add proxy credentials if your proxy requires authentication. Then enter the project name, select Run type as test set. Enter the Test Set ID and description from ALM and a timeslot duration in minutes.
This should be all you need to setup.
Marlene Macdonald
added a comment - 1) On Jenkins -> configuration: enter the name and URL of the ALM server under Application Lifecycle Management/ALM server
2) On Jenkins -> Plugin Manager -> Advanced: enter proxy server and port, plus optionally user/password if needed (if your proxy requires authentication) under HTTP Proxy Configuration
3) Create Item(job), Configure Build step as Execute HPE tests using HPE ALM Lab Management. Select ALM Server. Enter ALM Credentials. (Use Add button to setup first time. This is the user/password that connects to ALM) Enter Domain. Check the box "Use proxy settings". Enter your proxy address and port, x.x.x.x:80. Add proxy credentials if your proxy requires authentication. Then enter the project name, select Run type as test set. Enter the Test Set ID and description from ALM and a timeslot duration in minutes.
This should be all you need to setup. 
The automation tool doesn't use the system proxy settings. It uses the proxy settings in the specific step. For example in 'Execute HP tests using HP ALM Lab Management' step there are settings of proxy. Please try set the proxy there.