[JIRA] Created: (JENKINS-8998) Running the Quality Center Plugin from a Jenkins Server on Linux

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

[JIRA] Created: (JENKINS-8998) Running the Quality Center Plugin from a Jenkins Server on Linux

JIRA noreply@jenkins-ci.org
Running the Quality Center Plugin from a Jenkins Server on Linux
----------------------------------------------------------------

                 Key: JENKINS-8998
                 URL: http://issues.jenkins-ci.org/browse/JENKINS-8998
             Project: Jenkins
          Issue Type: Bug
          Components: qc
    Affects Versions: current
         Environment: We have a Jenkins Master server running on Linux (Open Suse), with a Jenkins Slave Agent running on Windows XP.
            Reporter: Shane Smart
            Assignee: rseguy
             Fix For: current


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?

--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] Work started: (JENKINS-8998) Running the Quality Center Plugin from a Jenkins Server on Linux

JIRA noreply@jenkins-ci.org

     [ http://issues.jenkins-ci.org/browse/JENKINS-8998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on JENKINS-8998 started by rseguy.

> Running the Quality Center Plugin from a Jenkins Server on Linux
> ----------------------------------------------------------------
>
>                 Key: JENKINS-8998
>                 URL: http://issues.jenkins-ci.org/browse/JENKINS-8998
>             Project: Jenkins
>          Issue Type: Bug
>          Components: qc
>    Affects Versions: current
>         Environment: We have a Jenkins Master server running on Linux (Open Suse), with a Jenkins Slave Agent running on Windows XP.
>            Reporter: Shane Smart
>            Assignee: rseguy
>             Fix For: current
>
>
> 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?

--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] Closed: (JENKINS-8998) Running the Quality Center Plugin from a Jenkins Server on Linux

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

     [ http://issues.jenkins-ci.org/browse/JENKINS-8998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

rseguy closed JENKINS-8998.
---------------------------


> Running the Quality Center Plugin from a Jenkins Server on Linux
> ----------------------------------------------------------------
>
>                 Key: JENKINS-8998
>                 URL: http://issues.jenkins-ci.org/browse/JENKINS-8998
>             Project: Jenkins
>          Issue Type: Bug
>          Components: qc
>    Affects Versions: current
>         Environment: We have a Jenkins Master server running on Linux (Open Suse), with a Jenkins Slave Agent running on Windows XP.
>            Reporter: Shane Smart
>            Assignee: rseguy
>             Fix For: current
>
>
> 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?

--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] Commented: (JENKINS-8998) Running the Quality Center Plugin from a Jenkins Server on Linux

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ http://issues.jenkins-ci.org/browse/JENKINS-8998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=146652#comment-146652 ]

rseguy commented on JENKINS-8998:
---------------------------------

NB: I use option #1.

> Running the Quality Center Plugin from a Jenkins Server on Linux
> ----------------------------------------------------------------
>
>                 Key: JENKINS-8998
>                 URL: http://issues.jenkins-ci.org/browse/JENKINS-8998
>             Project: Jenkins
>          Issue Type: Bug
>          Components: qc
>    Affects Versions: current
>         Environment: We have a Jenkins Master server running on Linux (Open Suse), with a Jenkins Slave Agent running on Windows XP.
>            Reporter: Shane Smart
>            Assignee: rseguy
>             Fix For: current
>
>
> 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?

--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] Resolved: (JENKINS-8998) Running the Quality Center Plugin from a Jenkins Server on Linux

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

     [ http://issues.jenkins-ci.org/browse/JENKINS-8998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

rseguy resolved JENKINS-8998.
-----------------------------

    Resolution: Fixed

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.

> Running the Quality Center Plugin from a Jenkins Server on Linux
> ----------------------------------------------------------------
>
>                 Key: JENKINS-8998
>                 URL: http://issues.jenkins-ci.org/browse/JENKINS-8998
>             Project: Jenkins
>          Issue Type: Bug
>          Components: qc
>    Affects Versions: current
>         Environment: We have a Jenkins Master server running on Linux (Open Suse), with a Jenkins Slave Agent running on Windows XP.
>            Reporter: Shane Smart
>            Assignee: rseguy
>             Fix For: current
>
>
> 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?

--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] Commented: (JENKINS-8998) Running the Quality Center Plugin from a Jenkins Server on Linux

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ http://issues.jenkins-ci.org/browse/JENKINS-8998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=146693#comment-146693 ]

Shane Smart commented on JENKINS-8998:
--------------------------------------

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

> Running the Quality Center Plugin from a Jenkins Server on Linux
> ----------------------------------------------------------------
>
>                 Key: JENKINS-8998
>                 URL: http://issues.jenkins-ci.org/browse/JENKINS-8998
>             Project: Jenkins
>          Issue Type: Bug
>          Components: qc
>    Affects Versions: current
>         Environment: We have a Jenkins Master server running on Linux (Open Suse), with a Jenkins Slave Agent running on Windows XP.
>            Reporter: Shane Smart
>            Assignee: rseguy
>             Fix For: current
>
>
> 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?

--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira