-
Bug
-
Resolution: Unresolved
-
Blocker
-
None
-
Jenkins 2.249.3
Micro Focus Application Automation Tools version 6.5
After upgrading Micro Focus Application Automation Tools plugin from version 6.2 version 6.5 on our jenkins, we are unable to connect to our ALM SaaS instance (version 15.01) using API key.
Each time we run a job, it failed. When checking the Console Output, we found this error message: "One or more of the required connection parameters is empty." Can someone indicate which parameter is missing? We have populated all the necessary field
We have created a new build in jenkins and in the Configuration System page, we have added our SSO credentials and in the build configuration we have selected the checkbox "SSO enable" and selected the "ALM Client ID" to use and also type in the path to the test set and under in which Domain and Project it can be found. (see attachements).
Multiple projects in our organization are depending of this plugin and right now no one can run there automated tests.
In the version 6.2 of the plugin, we are able to connect to our ALM SaaS instance using API keys but after upgrading to version 6.5 it has stopped working.
[JENKINS-64640] Connect to ALM SaaS via API Key does not work anymore
Sami Jansson
created issue -
Sami Jansson
made changes -
| Attachment | New: Console output plugin version 6.5.PNG [ 53836 ] |
Paul-Adrian Tofan
made changes -
| Assignee | Original: Paul-Adrian Tofan [ ptofan ] | New: Roy Lu [ roy_lu ] |
Paul-Adrian Tofan
made changes -
| Assignee | Original: Roy Lu [ roy_lu ] | New: Anda Sorina Laakso [ aslaakso ] |
Sami Jansson
added a comment - please, is there any update on this ticket? we weren't able to execute our test for more than a week. If there are no solution coming out before Tuesday 2020-01-26 then we will have no choice but to stop using Micro Focus since there are obviously not reliable.
/Sami
Sami Jansson
added a comment - please, is there any update on this ticket? we weren't able to execute our test for more than a week. If there are no solution coming out before Tuesday 2020-01-26 then we will have no choice but to stop using Micro Focus since there are obviously not reliable.
/Sami 
Anda Sorina Laakso
added a comment - Hi Sami,
As a first note and for further usage of the plugin, next time when you encounter an issue which blocks your automation testing processes, please open a CPE with the help of our support engineers. In this way, your ticket will be prioritized over Jira tickets and we can follow up work on the issue easier and establish meetings with you if needed.
Second item, I will take a look on this problem you are facing, since it is related to the jenkins plugin, so it should be handled by us, not by the ALM team.
Indeed compared to version 6.2 there has been a major update regarding the ALM credentials: the ALM credentials, both SSO and non-SSO, have been moved to Jenkins Configure System page. I assume you run the "Migrate ALM credentials job" before using them in your ALM job configuration page. Please make sure that you have both ALM Api key secret and ALM Client ID in Jenkins Configure System page and that they are setup properly also in UFT and still working ( both client ID and api key secret are still valid credentials - make a test a login separately with them in ALM).
If everything is setup correctly and connection with ALM is working outside the Jenkins plugin, we can setup a meeting if you want. Just let me know your availability and preference on Teams or Webex.
You can also email me directly to: anda-sorina.laakso@microfocus.com.
Note: send me by email also the param file ( props....txt).
Here is our updated documentation on using UFT, Jenkins and ALM :
https://admhelp.microfocus.com/uft/en/15.0-15.0.2/UFT_Help/Content/User_Guide/Jenkins.htm#mt-item-8
Thank you.
Anda Sorina Laakso
added a comment - Hi Sami,
As a first note and for further usage of the plugin, next time when you encounter an issue which blocks your automation testing processes, please open a CPE with the help of our support engineers. In this way, your ticket will be prioritized over Jira tickets and we can follow up work on the issue easier and establish meetings with you if needed.
Second item, I will take a look on this problem you are facing, since it is related to the jenkins plugin, so it should be handled by us, not by the ALM team.
Indeed compared to version 6.2 there has been a major update regarding the ALM credentials: the ALM credentials, both SSO and non-SSO, have been moved to Jenkins Configure System page. I assume you run the "Migrate ALM credentials job" before using them in your ALM job configuration page. Please make sure that you have both ALM Api key secret and ALM Client ID in Jenkins Configure System page and that they are setup properly also in UFT and still working ( both client ID and api key secret are still valid credentials - make a test a login separately with them in ALM).
If everything is setup correctly and connection with ALM is working outside the Jenkins plugin, we can setup a meeting if you want. Just let me know your availability and preference on Teams or Webex.
You can also email me directly to: anda-sorina.laakso@microfocus.com.
Note: send me by email also the param file ( props....txt).
Here is our updated documentation on using UFT, Jenkins and ALM :
https://admhelp.microfocus.com/uft/en/15.0-15.0.2/UFT_Help/Content/User_Guide/Jenkins.htm#mt-item-8
Thank you.
Hi Sorina
Did you receive the mail that I have send you last week?
Br
Sami
Sami Jansson
added a comment - - edited Hi Sorina
Did you receive the mail that I have send you last week?
Br
Sami Anda Sorina Laakso
added a comment - No, I did not receive any email and I was wondering if you have any updates. Please try to resend it. Thank you.
Anda Sorina Laakso
added a comment - No, I did not receive any email and I was wondering if you have any updates. Please try to resend it. Thank you. 
I have added a screenshot of the console output that display the error message that we got.
I can send you via mail the paramfile that the build is using, if you want too.