[
https://issues.jenkins-ci.org/browse/JENKINS-13152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160520#comment-160520
]
Ross Rowe commented on JENKINS-13152:
-------------------------------------
Okay, thanks for letting me know. Could you try stopping jenkins, removing the
~/.jenkins/plugins/sauce-ondemand directory, then restart jenkins? It looks
like Sauce Connect is still being started on the Slave, which shouldn't happen
with the snapshot version, so I think the old plugin logic is still active.
I'll do some further investigation into the NullPointerExceptions, could you
send me the config.xml files for your projects and I'll try to replicate the
issues.
Cheers,
Ross
> 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
