[JIRA] [hp-application-automation-tools-plugin] (JENKINS-19374) issue with HP Application Automation Tools plugin - error: Could not create scheduler, please verify ALM client installation on run mach
Title: Message Title Mark Davies commented on JENKINS-19374 Re: issue with HP Application Automation Tools plugin - error: Could not create scheduler, please verify ALM client installation on run machine by downloading and in installing the add-in form: http://Almserver:Portnumber/qcbin/TDConnectivity_index.html I agree Mark H. This is our findings as well. We are using a work around to starting the slave as a service. We are using the Windows Task scheduler to start the JNLP slave at windows startup so at least if the machine restarts the Slave will restart as well. Not ideal but got us going until the Plugin owners get a chance to find a solution to running as a service. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hp-application-automation-tools-plugin] (JENKINS-19374) issue with HP Application Automation Tools plugin - error: Could not create scheduler, please verify ALM client installation on run mach
Title: Message Title Mark Davies commented on JENKINS-19374 Re: issue with HP Application Automation Tools plugin - error: Could not create scheduler, please verify ALM client installation on run machine by downloading and in installing the add-in form: http://Almserver:Portnumber/qcbin/TDConnectivity_index.html We are also experiencing exactly the same issue. Have removed all instances of ALM Client from the machine, then registered the client again with http://:8080/qcbin/start_a.jsp?Common=true. I note that if i launch the HpToolsLauncher.exe -paramfile from a command prompt (using the same user that is running the Jenkins service) it executes successfully and records the run in ALM. This would suggest the ALM client is working ok. Perhaps the issue is in the way the plugin is spawning child processes under Jenkins. Any updates or suggestions on this issue would be appreciated. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
