Closed bootstraponline closed 9 years ago
according to this commit it should be one Sauce Connect for all tests. I added debugging information and it looks like there's a race condition (in addition to an infinite loop which I filed in a new issue) and it's easy to have two Sauce Connects startup when there should only be one.
Ideally I'd be able to use the Jenkins plugin which actually works and not have to bother with the Ruby sauce connect logic.
I checked Launch Sauce Connect on Slave
and now I'm able to use the Java plugin to start/stop the Sauce Connect tunnel reliably on Jenkins bypassing the buggy ruby code.
I can't get sauce_ruby to talk to Sauce Connect started by the Sauce Jenkins OnDemand plugin. Sauce Connect only works if it's started via Ruby. I think we only need one Sauce Connect for all the tests, right?