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

Running the Quality Center Plugin from a Jenkins Server on Linux

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: qc-plugin
    • Labels:
      None
    • Environment:
      We have a Jenkins Master server running on Linux (Open Suse), with a Jenkins Slave Agent running on Windows XP.
    • Similar Issues:

      Description

      We would like to use the Jenkins QC plugin from our master Jenkins server that is running on Linux. Running a job through our windows slave that connects to QC and runs some QTP tests. I see no reason why this shouldn't work, however the main configuration of the QC plugin (on the linux server) requires a local path to both a Quality Center client and a QuickTest Professional Add-in. Being Linux there is no such paths.

      Is there any way of providing this configuration for the slave agent?

        Attachments

          Activity

          Hide
          cramer Shane Smart added a comment -

          Thanks for the prompt reply. We went for option 1 which worked a treat.

          Show
          cramer Shane Smart added a comment - Thanks for the prompt reply. We went for option 1 which worked a treat.
          Hide
          rseguy Romain Seguy added a comment -

          NB: I use option #1.

          Show
          rseguy Romain Seguy added a comment - NB: I use option #1.
          Hide
          rseguy Romain Seguy added a comment -

          There are two ways to do so:

          1. Put the Windows paths pointing to your installs in Jenkins' main configuration screen (and simply ignore the validation messages saying the path is wrong).
          2. Put a fake value for each required path in Jenkins' main configuration screen, and, then, for your slave, override the location in the slave configuration screen.
          Show
          rseguy Romain Seguy added a comment - There are two ways to do so: Put the Windows paths pointing to your installs in Jenkins' main configuration screen (and simply ignore the validation messages saying the path is wrong). Put a fake value for each required path in Jenkins' main configuration screen, and, then, for your slave, override the location in the slave configuration screen.

            People

            Assignee:
            rseguy Romain Seguy
            Reporter:
            cramer Shane Smart
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: