Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-25464

Unable to Run HP LoadRunner from Jenkins in a Master/Slave Configuration

    • Icon: Task Task
    • Resolution: Not A Defect
    • Icon: Major Major

      Trying to set up running HP LoadRunner Controller Scenario to run in a Jenkins Master/Slave configuration for Continuous Integration (CI) proof of concept work. The Controller Scenario runs correctly in a Local Jenkins/LoadRunner installation (i.e. both Jenkins and HP LoadRunner installed on the same machine). When trying to do a "Build Now" from Jenkins in the Master/Slave setup, the test ends with one word: Error.

      If there is additional logged information besides the word "Error", I have not yet found it.

          [JENKINS-25464] Unable to Run HP LoadRunner from Jenkins in a Master/Slave Configuration

          I may have found the issue with this problem. It seems related to how the Path to the Controller Scenario is entered in the Jenkins setup. I will try variations to verify this.

          Randy Stevenson added a comment - I may have found the issue with this problem. It seems related to how the Path to the Controller Scenario is entered in the Jenkins setup. I will try variations to verify this.

          There's a great post on Stack Overflow with steps for setting up a Master/Slave environment.
          http://stackoverflow.com/questions/27438928/running-hp-load-runeer-from-jenkins

          This may not directly relate to your issue, but maybe there is some helpful info.

          Connor Gilbert added a comment - There's a great post on Stack Overflow with steps for setting up a Master/Slave environment. http://stackoverflow.com/questions/27438928/running-hp-load-runeer-from-jenkins This may not directly relate to your issue, but maybe there is some helpful info.

          This was not a defect with the Plugin. Instead, it was a configuration issue with the Jenkins slave.

          Randy Stevenson added a comment - This was not a defect with the Plugin. Instead, it was a configuration issue with the Jenkins slave.

            randystevenson Randy Stevenson
            randystevenson Randy Stevenson
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: