if users run multiple builds in parallel after setting the the selenium host as 0 (to generate a random port) the plugin often generates the same port for each build causing sauce connect to crash.
this issue was easy to replicate and happened frequently
Solution:
remove the breaking code. if the selenium host is 0, sauce connect will look for an open port to run on. The code removed was forcing sauce connect to use a specific port that may not be available at the time sauce connect is launched, especially if multiple tunnels are started simultaneously.
if users run multiple builds in parallel after setting the the selenium host as 0 (to generate a random port) the plugin often generates the same port for each build causing sauce connect to crash.
Solution: remove the breaking code. if the selenium host is 0, sauce connect will look for an open port to run on. The code removed was forcing sauce connect to use a specific port that may not be available at the time sauce connect is launched, especially if multiple tunnels are started simultaneously.