[
https://issues.jenkins-ci.org/browse/JENKINS-13152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160463#comment-160463
]
Ross Rowe commented on JENKINS-13152:
-------------------------------------
Okay, thanks for that, I've updated the summary and description to cover this.
In this case, I think the change should be fairly straightforward...I think
I'll try change the plugin to launch Sauce Connect on the Master, then all you
will need to do is configure the Job to include the host name of the Master in
the Sauce Connect Advanced Options.
I'll let you know when I've got a snapshot version ready to test.
> Multiple Sauce Connect instance are launched when multiple Slaves are used
> --------------------------------------------------------------------------
>
> Key: JENKINS-13152
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13152
> Project: Jenkins
> Issue Type: Improvement
> Components: sauce-ondemand
> Reporter: Ross Rowe
> Assignee: Ross Rowe
>
> From http://support.saucelabs.com/requests/1892
> The plugin supports a single Sauce Connect instance, but this is controlled
> via variables specific to each slave JVM instance. Multiple slaves will
> therefore launch multiple instances of Sauce Connect.
> The plugin should be updated to ensure that only a single Sauce Connect
> instance (per Sauce user) is instantiated across all slaves running.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
