Unable to successfully execute script from HP ALM using jenkins add-on

1,103 views
Skip to first unread message

Zeljko Jurkovic

unread,
May 8, 2013, 2:57:00 PM5/8/13
to jenkins...@googlegroups.com
I'm getting following error message when trying to execute script on slave computer from HP ALM server using jenkins add-on:

Could not create scheduler, please verify ALM client installation on run machine by downloading and in installing the add-in form: http://hpalm1/qcbin/TDConnectivity_index.html

The TD connectivity add-on is installed on slave. I can  only reinstall it (with same result).
When I execute script on slave through cmd ( c:\CIJenkins\.jenkins\workspace\ALM-TEST1\HpToolsLauncher.exe -paramfile props08052013152607062.txt ) works fine.

If anyone knows the solution, please help.

Arun Batra

unread,
Jul 26, 2015, 5:07:54 AM7/26/15
to Jenkins Users, zeljko....@gmail.com
Hi Zhar,

I understand this is pretty old but i have to ask, Did you find a solution to this? I am facing the same issue?
Any hints would be grateful.


Roman Shchekin

unread,
Jun 1, 2016, 3:47:51 AM6/1/16
to Jenkins Users, zeljko....@gmail.com
Do you have any solution for this?
I am facing it right now.

воскресенье, 26 июля 2015 г., 12:07:54 UTC+3 пользователь Arun Batra написал:

Arun Batra

unread,
Jun 1, 2016, 4:29:50 AM6/1/16
to Jenkins Users
Hi Roman,
I got it working by running the jenkins slave as a UI. You know the one that runs from the browser and starts java and opens a small window which says connected. (I automated this startup later). It was not running for me before because I was running the slave as a Windows service.
Hope this helps.

Zhar

unread,
Jun 1, 2016, 4:31:33 AM6/1/16
to Jenkins Users, zeljko....@gmail.com
Hi,
I've changed a company a year ago and haven't been using Jenkins since.
But...If I remember correctly problem was in the user which was registered to hp alm, and the user which was used by Jenkins.
You need to register user, the one which will execute test, to hpalm and install add-in for him (Basically you should perform registration procedure for each user which is going to execute tests).
That was solution in my case.

Arun Batra found this as the solution:

I was running Jenkins slave as a service.. Turned out that services do not interact with the desktop. So unable to start scheduler.. I started using the UI or the command prompt.. It worked! 


Hope this helps.
Cheers,
Zeljko
Reply all
Reply to author
Forward
0 new messages