blade-sauce_labs_plugin 0.5.2 → 0.5.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 36b3598b5eaa5726a03629ec518e327f316bd556
-  data.tar.gz: f30ffedd23ac0dc98cb70bf3135690bc92b0bacc
+  metadata.gz: 3977ba73eab86543539631e96c9dc25a55eb4f12
+  data.tar.gz: af389e81192ba197558b643af01e3deb1e4f1e5d
 SHA512:
-  metadata.gz: c7acce2a43bc42c59722174128be43291d8018f0480c02ae85b6d506cc44ce1ede98d46c62bb8bc78c95b1619a61e9d063e74820dcb723c4cea78f14fe276631
-  data.tar.gz: b91a3980daba289f58775c094e6eae01d13c1dd6b1efe842fd2033feb76eb1d28b2df2cffc1b3b5855a6768b38c12c116b0dce1febd1ff442f14e69fdbbff3e7
+  metadata.gz: 5ea529d7521022b7465531ee078613637814d28467420afcb3c85d8b1fc3306078822c68cb8b3d07151d01108caac502890b91268e7aff54eab512c641ee7667
+  data.tar.gz: 17d01ba5bbd1322443e0787d3c6d7c05287c233ef1cfea754be9011719f69e1068dacb5c773ccfba54aa8ea5af0e3a8024893e36afe6fb4607954d271124dadc

data/lib/blade/sauce_labs_plugin.rb

@@ -60,6 +60,10 @@ module Blade::SauceLabsPlugin
     ENV["SAUCE_ACCESS_KEY"] || config.access_key
   end
 
+  def tunnel_timeout
+    (ENV["SAUCE_TUNNEL_TIMEOUT"] || config.tunnel_timeout || 60).to_i
+  end
+
   def debug(message)
     if debug?
       STDERR.puts message

data/lib/blade/sauce_labs_plugin/tunnel.rb

@@ -5,7 +5,7 @@ module Blade::SauceLabsPlugin::Tunnel
   extend self
 
   extend Forwardable
-  def_delegators Blade::SauceLabsPlugin, :username, :access_key, :config, :debug, :debug?
+  def_delegators Blade::SauceLabsPlugin, :username, :access_key, :tunnel_timeout, :config, :debug, :debug?
 
   attr_reader :identifier, :process
 
@@ -13,16 +13,26 @@ module Blade::SauceLabsPlugin::Tunnel
     @identifier = SecureRandom.hex(10)
     @process = create_child_process
 
+    started_at = Time.now
     timer = EM::PeriodicTimer.new(1) do
       if ready_file_exists?
         timer.cancel
         yield
+      elsif !debug?
+        elapsed = Time.now - started_at
+        if elapsed > tunnel_timeout
+          timer.cancel
+          STDERR.puts "Failed to establish tunnel connection after #{elapsed}s:\n#{logs}"
+          STDERR.puts tunnel_io.tap(&:rewind).read
+          exit(1)
+        end
       end
     end
   end
 
   def stop
     begin
+      tunnel_io.unlink
       process.poll_for_exit(10)
     rescue ChildProcess::TimeoutError
       process.stop
@@ -34,8 +44,13 @@ module Blade::SauceLabsPlugin::Tunnel
   private
     def create_child_process
       ChildProcess.build(tunnel_command, *tunnel_args).tap do |process|
+        if debug?
+          process.io.inherit!
+        else
+          process.io.stdout = process.io.stderr = tunnel_io
+          process.duplex = true
+        end
         process.leader = true
-        process.io.inherit! if debug?
         process.environment.merge! tunnel_env
         process.start
         debug process.inspect
@@ -54,6 +69,10 @@ module Blade::SauceLabsPlugin::Tunnel
       { "SAUCE_USERNAME" => username, "SAUCE_ACCESS_KEY" => access_key }
     end
 
+    def tunnel_io
+      @tunnel_io ||= Tempfile.new("blade_sauce_tunel_#{identifier}").tap { |io| io.sync = true }
+    end
+
     def ready_file_path
       Blade.tmp_path.join("sauce_tunnel_#{identifier}_ready").to_s
     end

data/lib/blade/sauce_labs_plugin/version.rb

@@ -1,5 +1,5 @@
 module Blade
   module SauceLabsPlugin
-    VERSION = "0.5.2"
+    VERSION = "0.5.3"
   end
 end

data/support/sc-linux/config/systemd/README.md

@@ -0,0 +1,83 @@
+Systemd is a system and service manager for Linux that, among other things, can be used to control the starting and stopping of services. For more information check out https://www.freedesktop.org/wiki/Software/systemd/
+
+Sauce Connect is a secure tunneling application that allows the Sauce Labs browser cloud to connect to websites you want to test that are hosted on localhost or behind a firewall. For more information check out the Sauce Labs documentation wiki: https://wiki.saucelabs.com/display/DOCS/Sauce+Connect
+
+These instructions will show you how to set up systemd with Sauce Connect to manage the starting and stopping of Sauce Connect tunnels.
+
+Systemd will automatically start the Sauce Connect service, monitor each client, and tranparently restart the client if the client gets disconnected or a tunnel goes down.
+
+Setting Up systemd
+----------------
+
+1. Copy the files `sc.service` & `sc@.service` to `/etc/systemd/system`.
+2. Create a directory `sc.service.wants` in `/etc/systemd/system`.
+   You'll have to create symbolic links inside this directory to set up new instances of Sauce
+Connect. For example, if you'd like to have two Sauce Connect instances listening on
+port 8000 & 8001:
+```
+    $ cd /etc/systemd/system/
+    $ sudo mkdir -p ./sc.service.wants
+    $ sudo ln -s /etc/systemd/system/sc@.service ./sc.service.wants/sc@8000.service
+    $ sudo ln -s /etc/systemd/system/sc@.service ./sc.service.wants/sc@8001.service
+```
+3. Add your Saucelabs credentials to `/etc/systemd/system/sc@.service` in the
+   service section like this:
+```
+    Environment=SAUCE_USERNAME=myusername
+    Environment=SAUCE_ACCESS_KEY=fd69b0a8-337c-3303-b1bd-xxxxxxxxxxx
+```
+
+Starting and Stopping the Service
+---------------------
+After you have configured the instances, you can start up the new service:
+```
+    # This is important otherwise systemd won't pick up the new configuration
+    $ sudo systemctl daemon-reload
+    $ sudo systemctl start sc
+    $ sudo systemctl status sc
+    ● sc.service - Sauce Connect workers hypervisor
+       Loaded: loaded (/etc/systemd/system/sc.service; disabled; vendor preset: enabled)
+       Active: active (exited) since Wed 2016-04-06 17:44:37 PDT; 6s ago
+    ...
+
+    $ sudo systemctl status 'sc@*'
+    ● sc@8000.service - Sauce Connect worker service on port 8000
+       Loaded: loaded (/etc/systemd/system/sc@.service; enabled; vendor preset: enabled)
+       Active: active (running) since Wed 2016-04-06 17:44:37 PDT; 23s ago
+    ...
+    Apr 06 17:44:50 usery-BigFatServerzz sc[6772]: 20160406 174450.926 [06772] Sauce Connect is up, you may start your tests.
+```
+To stop all the instances:
+```
+    $ sudo systemctl stop sc
+```
+Managing Individual Instances
+-----------------------------
+You can also manage invididual instance without impacting the other instances by using the syntax `sc@<PORT NUMBER>`. For example, here's how you'd manage the instance listening on port 8000:
+```
+    $ sudo systemctl status 'sc@8000.service'
+    ● sc@8000.service - Sauce Connect worker service on port 8000
+       Loaded: loaded (/etc/systemd/system/sc@.service; enabled; vendor preset: enabled)
+       Active: active (running) since Wed 2016-04-06 17:44:37 PDT; 5min ago
+    ...
+
+
+    # This won't affect the other instances
+    $ sudo systemctl restart 'sc@8000.service'
+    
+```
+Systemd Tips and Tricks
+=====================
+
+When working with systemd I recommend making an alias for systemctl to automate
+the configuration reload:
+
+    function sd() {
+        sudo systemctl daemon-reload > /dev/null
+        sudo systemctl $@
+    }
+
+When debugging problems with a unit:
+
+    $ systemctl status unit
+    $ journalctl -xe -u unit

data/support/sc-linux/config/systemd/sc.service

@@ -0,0 +1,16 @@
+#
+# Start & stop Sauce Connect workers
+#
+[Unit]
+Description=Sauce Connect workers hypervisor
+After=network.target
+
+[Service]
+Type=oneshot
+RemainAfterExit=yes
+ExecStart=/bin/true
+ExecReload=/bin/true
+WorkingDirectory=/tmp
+
+[Install]
+WantedBy=multi-user.target

data/support/sc-linux/config/systemd/sc@.service

@@ -0,0 +1,28 @@
+[Unit]
+Description=Sauce Connect worker service on port %i
+PartOf=sc.service
+ReloadPropagatedFrom=sc.service
+
+[Service]
+  Type=simple
+  User=nobody
+  Group=nogroup
+  WorkingDirectory=/tmp
+  LimitNOFILE=8192
+  Restart=always
+
+  # Set those to match your Saucelabs credentials
+  Environment=SAUCE_USERNAME=username
+  Environment=SAUCE_ACCESS_KEY=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
+
+  ExecStart = /usr/local/bin/sc \
+                --logfile - \
+                --pidfile "/tmp/sauceconnect_%i.pid" \
+                --se-port "%i" \
+                --no-remove-colliding-tunnels \
+                --wait-tunnel-shutdown
+  # Not needed with systemd
+  ExecStartPost = /bin/rm -f /tmp/sauceconnect_%i.pid
+
+[Install]
+WantedBy=multi-user.target

data/support/sc-linux/config/upstart/README.md

@@ -0,0 +1,76 @@
+Upstart is an event-based replacement for the `/sbin/init` Linux daemon that handles starting of tasks and services during boot, stopping them during shutdown, and supervising them while the system is running. For more information check out http://upstart.ubuntu.com.
+
+Upstart will automatically start the Sauce Connect service, monitor each client, and tranparently restart the client if the client gets disconnected or a tunnel goes down.
+
+Sauce Connect is a secure tunneling application that enables the Sauce Labs browser cloud to connect with websites you want to test that are hosted on your local machine or behind a firewall.
+
+These instructions will help you set up Sauce Connect so that the starting and stopping of tunnels is controlled by Upstart.
+
+1. Install the Sauce connect binary to `/usr/local/bin/sc`.
+2. Copy the `sc_worker.conf` & `sc.conf` files to `/etc/init`.
+   This will create two new upstart services, `sc_worker` and `sc.conf`. `sc_worker` manages individual Sauce Connect instance, while `sc.conf` manages multiple-instances started with `sc_worker`, allowing you to start multiple instances on the same server.
+3. Check that the services are installed correctly with the `initctl list` command:
+```
+    $ initctl list | grep '^sc'
+    sc_worker stop/waiting
+    sc stop/waiting
+```
+4. Create a file named `/etc/default/sc` to store Sauce Connect's configuration options.
+   It should look something like that:
+```
+    SAUCE_USERNAME=username
+    SAUCE_ACCESS_KEY=fd698b0a-744c-4205-pa3d-16e2734127bf
+```
+Single Instance
+---------------
+
+Once that's done you can start and stop invidual Sauce Connect instance like this:
+```
+    $ sudo start sc_worker SE_PORT=8888
+    sc_worker (8888) start/running, process 8856
+```
+The value `SE_PORT` corresponds to the Selenium port, each instance must have a
+unique Seleniun port to listen on.
+
+Let's check that our instace was started properly:
+
+    $ status sc_worker SE_PORT=8888
+    sc_worker (8888) start/running, process 8856
+
+Looks all good, you now have a single instance of Sauce Connect running. If the
+tunnel closes or anything unexpected happens upstart will automatically restart
+Sauce Connect to re-establish connectivity.
+
+Multiple Instances
+------------------
+
+While single instance setups are perfectly acceptable for small scale operations, you should set up multiple instances of Sauce Connect with High Availability to improve reliability & performance. For more information about the High Availability configuration for Sauce Connect, check our our documentation wiki: https://wiki.saucelabs.com/display/DOCS/Sauce+Connect
+
+To use multiple instances, edit `/etc/default/sc` and add the parameter `SE_PORTS`
+like this:
+```
+    SAUCE_USERNAME=username
+    SAUCE_ACCESS_KEY=fd698b0a-744c-4205-pa3d-16e2734127bf
+    SE_PORTS='8000 8001 8002 8003'
+```
+This will create four Sauce Connect instances, listening on port 8000, 8001, 8002,
+& 8003. Let's try it out with the `sc` service:
+```
+    $ sudo start sc
+    sc start/running
+```
+Let's check the status of the `sc_worker` services:
+```
+    $ initctl list | grep sc_worker
+    sc_worker (8001) start/running, process 8503
+    sc_worker (8000) start/running, process 8500
+    sc_worker (8003) start/running, process 8512
+    sc_worker (8002) start/running, process 8508
+```
+Stopping those instances is the same as starting them:
+```
+    $ sudo stop sc
+    sc stop/waiting
+    $ initctl list | grep sc_worker
+    sc_worker stop/waiting
+```

data/support/sc-linux/config/upstart/sc.conf

@@ -0,0 +1,29 @@
+# vim:ft=upstart:
+description "SauceLabs' Sauce Connect tunnel worker supervisor service"
+
+start on runlevel [2345]
+stop on runlevel [016]
+
+pre-start script
+    # Load configuration
+    test -r /etc/default/sc || { stop; exit 0; }
+    . /etc/default/sc
+    test -n "$SE_PORTS" || { stop; exit 1; }
+
+    for se_port in $SE_PORTS
+    do
+        start sc_worker SE_PORT=$se_port
+    done
+end script
+
+post-stop script
+    # Load configuration
+    test -r /etc/default/sc || { stop; exit 0; }
+    . /etc/default/sc
+    test -n "$SE_PORTS" || { stop; exit 1; }
+
+    for se_port in $SE_PORTS
+    do
+        stop sc_worker SE_PORT=$se_port || true  # ignore shutdown instances
+    done
+end script

data/support/sc-linux/config/upstart/sc_worker.conf

@@ -0,0 +1,59 @@
+#
+# This Upstart config expects that Sauce Connect (SC) is installed at
+# /usr/local/bin/sc. Edit that path if it is installed somewhere else.
+#
+# Copy this file to /etc/init/sc.conf, and do:
+#
+# $ sudo initctl reload-configuration
+#
+# Then you can manage SC via the usual upstart tools, e.g.:
+#
+#   $ sudo start sc
+#   $ sudo restart sc
+#   $ sudo stop sc
+#   $ sudo status sc
+#
+
+description "SauceLabs' Sauce Connect tunnel worker service"
+
+instance $SE_PORT
+usage "SE_PORT - selenium port"
+
+stop on stopping sc
+
+setuid nobody
+setgid nogroup
+chdir /tmp
+# Restart Sauce Connect if it exits
+respawn
+# Sauce Connect output go to $logdir/sc.log.
+console log
+# Bump maximum number of open files/sockets.
+limit nofile 8192 8192
+
+# Sauce Connect will be killed if doesn't stop within 2 minutes. SC usually
+# exits much faster than 2 minutes but it can occasionally get stuck if the
+# connectivity between SC & Saucelabs is interupted.
+kill timeout 120
+
+script
+        # Load configuration
+        test -r /etc/default/sc || { stop; exit 0; }
+        . /etc/default/sc
+
+        # Temporary PID file since it's a required option for SauceConnect
+        pidfile="/tmp/.sauceconnect_$SE_PORT.pid"
+        exec \
+        env \
+           SAUCE_USERNAME="$SAUCE_USERNAME" \
+           SAUCE_ACCESS_KEY="$SAUCE_ACCESS_KEY" \
+        /usr/local/bin/sc \
+                --logfile - \
+                --pidfile "$pidfile" \
+                --se-port "$SE_PORT" \
+                --no-remove-colliding-tunnels \
+                --wait-tunnel-shutdown
+end script
+
+# Remove PID file once we've started the service since it's not needed
+post-start exec rm -f "/tmp/.sauceconnect_$SE_PORT.pid"

data/support/sc-osx/config/systemd/README.md

@@ -0,0 +1,76 @@
+Systemd is a system and service manager for Linux that, among other things, can be used to control the starting and stopping of services. For more information check out https://www.freedesktop.org/wiki/Software/systemd/
+
+Sauce Connect is a secure tunneling application that allows the Sauce Labs browser cloud to connect to websites you want to test that are hosted on localhost or behind a firewall. For more information check out the Sauce Labs documentation wiki: https://wiki.saucelabs.com/display/DOCS/Sauce+Connect
+
+These instructions will show you how to set up systemd with Sauce Connect to manage the starting and stopping of Sauce Connect tunnels.
+
+Systemd will automatically start the Sauce Connect service, monitor each client, and tranparently restart the client if the client gets disconnected or a tunnel goes down.
+
+Setting Up systemd
+----------------
+
+1. Copy the files `sc.service` & `sc@.service` to `/etc/systemd/system`.
+2. Create a directory `sc.service.wants` in `/etc/systemd/system`.
+   You'll have to create symbolic links inside this directory to set up new instances of Sauce
+Connect. For example, if you'd like to have two Sauce Connect instances listening on
+port 8000 & 8001:
+```
+    $ cd /etc/systemd/system/
+    $ sudo mkdir -p ./sc.service.wants
+    $ sudo ln -s /etc/systemd/system/sc@.service ./sc.service.wants/sc@8000.service
+    $ sudo ln -s /etc/systemd/system/sc@.service ./sc.service.wants/sc@8001.service
+```
+Starting and Stopping the Service
+---------------------
+After you have configured the instances, you can start up the new service:
+```
+    # This is important otherwise systemd won't pick up the new configuration
+    $ sudo systemctl daemon-reload
+    $ sudo systemctl start sc
+    $ sudo systemctl status sc
+    ● sc.service - Sauce Connect workers hypervisor
+       Loaded: loaded (/etc/systemd/system/sc.service; disabled; vendor preset: enabled)
+       Active: active (exited) since Wed 2016-04-06 17:44:37 PDT; 6s ago
+    ...
+
+    $ sudo systemctl status 'sc@*'
+    ● sc@8000.service - Sauce Connect worker service on port 8000
+       Loaded: loaded (/etc/systemd/system/sc@.service; enabled; vendor preset: enabled)
+       Active: active (running) since Wed 2016-04-06 17:44:37 PDT; 23s ago
+    ...
+    Apr 06 17:44:50 usery-BigFatServerzz sc[6772]: 20160406 174450.926 [06772] Sauce Connect is up, you may start your tests.
+```
+To stop all the instances:
+```
+    $ sudo systemctl stop sc
+```
+Managing Individual Instances
+-----------------------------
+You can also manage invididual instance without impacting the other instances by using the syntax `sc@<PORT NUMBER>`. For example, here's how you'd manage the instance listening on port 8000:
+```
+    $ sudo systemctl status 'sc@8000.service'
+    ● sc@8000.service - Sauce Connect worker service on port 8000
+       Loaded: loaded (/etc/systemd/system/sc@.service; enabled; vendor preset: enabled)
+       Active: active (running) since Wed 2016-04-06 17:44:37 PDT; 5min ago
+    ...
+
+
+    # This won't affect the other instances
+    $ sudo systemctl restart 'sc@8000.service'
+    
+```
+Systemd Tips and Tricks
+=====================
+
+When working with systemd I recommend making an alias for systemctl to automate
+the configuration reload:
+
+    function sd() {
+        sudo systemctl daemon-reload > /dev/null
+        sudo systemctl $@
+    }
+
+When debugging problems with a unit:
+
+    $ systemctl status unit
+    $ journalctl -xe -u unit

data/support/sc-osx/config/systemd/sc.service

@@ -0,0 +1,16 @@
+#
+# Start & stop Sauce Connect workers
+#
+[Unit]
+Description=Sauce Connect workers hypervisor
+After=network.target
+
+[Service]
+Type=oneshot
+RemainAfterExit=yes
+ExecStart=/bin/true
+ExecReload=/bin/true
+WorkingDirectory=/tmp
+
+[Install]
+WantedBy=multi-user.target

data/support/sc-osx/config/systemd/sc@.service

@@ -0,0 +1,25 @@
+[Unit]
+Description=Sauce Connect worker service on port %i
+PartOf=sc.service
+ReloadPropagatedFrom=sc.service
+
+[Service]
+  Type=simple
+  User=nobody
+  Group=nogroup
+  WorkingDirectory=/tmp
+  LimitNOFILE=8192
+
+  EnvironmentFile=/etc/default/sc
+  ExecStart = /usr/local/bin/sc \
+                --logfile - \
+                --user "$SAUCE_USERNAME" \
+                --api-key "$SAUCE_ACCESS_KEY" \
+                --pidfile "/tmp/.sauceconnect_%i.pid" \
+                --se-port "%i" \
+                --no-remove-colliding-tunnels \
+                --wait-tunnel-shutdown
+  # ExecStartPost = /bin/rm -f /tmp/.sauceconnect_%i.pid
+
+[Install]
+WantedBy=multi-user.target

data/support/sc-osx/config/upstart/README.md

@@ -0,0 +1,76 @@
+Upstart is an event-based replacement for the `/sbin/init` Linux daemon that handles starting of tasks and services during boot, stopping them during shutdown, and supervising them while the system is running. For more information check out http://upstart.ubuntu.com.
+
+Upstart will automatically start the Sauce Connect service, monitor each client, and tranparently restart the client if the client gets disconnected or a tunnel goes down.
+
+Sauce Connect is a secure tunneling application that enables the Sauce Labs browser cloud to connect with websites you want to test that are hosted on your local machine or behind a firewall.
+
+These instructions will help you set up Sauce Connect so that the starting and stopping of tunnels is controlled by Upstart.
+
+1. Install the Sauce connect binary to `/usr/local/bin/sc`.
+2. Copy the `sc_worker.conf` & `sc.conf` files to `/etc/init`.
+   This will create two new upstart services, `sc_worker` and `sc.conf`. `sc_worker` manages individual Sauce Connect instance, while `sc.conf` manages multiple-instances started with `sc_worker`, allowing you to start multiple instances on the same server.
+3. Check that the services are installed correctly with the `initctl list` command:
+```
+    $ initctl list | grep '^sc'
+    sc_worker stop/waiting
+    sc stop/waiting
+```
+4. Create a file named `/etc/default/sc` to store Sauce Connect's configuration options.
+   It should look something like that:
+```
+    SAUCE_USERNAME=username
+    SAUCE_ACCESS_KEY=fd698b0a-744c-4205-pa3d-16e2734127bf
+```
+Single Instance
+---------------
+
+Once that's done you can start and stop invidual Sauce Connect instance like this:
+```
+    $ sudo start sc_worker SE_PORT=8888
+    sc_worker (8888) start/running, process 8856
+```
+The value `SE_PORT` corresponds to the Selenium port, each instance must have a
+unique Seleniun port to listen on.
+
+Let's check that our instace was started properly:
+
+    $ status sc_worker SE_PORT=8888
+    sc_worker (8888) start/running, process 8856
+
+Looks all good, you now have a single instance of Sauce Connect running. If the
+tunnel closes or anything unexpected happens upstart will automatically restart
+Sauce Connect to re-establish connectivity.
+
+Multiple Instances
+------------------
+
+While single instance setups are perfectly acceptable for small scale operations, you should set up multiple instances of Sauce Connect with High Availability to improve reliability & performance. For more information about the High Availability configuration for Sauce Connect, check our our documentation wiki: https://wiki.saucelabs.com/display/DOCS/Sauce+Connect
+
+To use multiple instances, edit `/etc/default/sc` and add the parameter `SE_PORTS`
+like this:
+```
+    SAUCE_USERNAME=username
+    SAUCE_ACCESS_KEY=fd698b0a-744c-4205-pa3d-16e2734127bf
+    SE_PORTS='8000 8001 8002 8003'
+```
+This will create four Sauce Connect instances, listening on port 8000, 8001, 8002,
+& 8003. Let's try it out with the `sc` service:
+```
+    $ sudo start sc
+    sc start/running
+```
+Let's check the status of the `sc_worker` services:
+```
+    $ initctl list | grep sc_worker
+    sc_worker (8001) start/running, process 8503
+    sc_worker (8000) start/running, process 8500
+    sc_worker (8003) start/running, process 8512
+    sc_worker (8002) start/running, process 8508
+```
+Stopping those instances is the same as starting them:
+```
+    $ sudo stop sc
+    sc stop/waiting
+    $ initctl list | grep sc_worker
+    sc_worker stop/waiting
+```

data/support/sc-osx/config/upstart/sc.conf

@@ -0,0 +1,29 @@
+# vim:ft=upstart:
+description "SauceLabs' Sauce Connect tunnel worker supervisor service"
+
+start on runlevel [2345]
+stop on runlevel [016]
+
+pre-start script
+    # Load configuration
+    test -r /etc/default/sc || { stop; exit 0; }
+    . /etc/default/sc
+    test -n "$SE_PORTS" || { stop; exit 1; }
+
+    for se_port in $SE_PORTS
+    do
+        start sc_worker SE_PORT=$se_port
+    done
+end script
+
+post-stop script
+    # Load configuration
+    test -r /etc/default/sc || { stop; exit 0; }
+    . /etc/default/sc
+    test -n "$SE_PORTS" || { stop; exit 1; }
+
+    for se_port in $SE_PORTS
+    do
+        stop sc_worker SE_PORT=$se_port || true  # ignore shutdown instances
+    done
+end script

data/support/sc-osx/config/upstart/sc_worker.conf

@@ -0,0 +1,57 @@
+#
+# This Upstart config expects that Sauce Connect (SC) is installed at
+# /usr/local/bin/sc. Edit that path if it is installed somewhere else.
+#
+# Copy this file to /etc/init/sc.conf, and do:
+#
+# $ sudo initctl reload-configuration
+#
+# Then you can manage SC via the usual upstart tools, e.g.:
+#
+#   $ sudo start sc
+#   $ sudo restart sc
+#   $ sudo stop sc
+#   $ sudo status sc
+#
+
+description "SauceLabs' Sauce Connect tunnel worker service"
+
+instance $SE_PORT
+usage "SE_PORT - selenium port"
+
+stop on stopping sc
+
+setuid nobody
+setgid nogroup
+chdir /tmp
+# Restart Sauce Connect if it exits
+respawn
+# Sauce Connect output go to $logdir/sc.log.
+console log
+# Bump maximum number of open files/sockets.
+limit nofile 8192 8192
+
+# Sauce Connect will be killed if doesn't stop within 2 minutes. SC usually
+# exits much faster than 2 minutes but it can occasionally get stuck if the
+# connectivity between SC & Saucelabs' is degraded/interupted.
+kill timeout 120
+
+script
+        # Load configuration
+        test -r /etc/default/sc || { stop; exit 0; }
+        . /etc/default/sc
+
+        # Temporary PID file since it's a required option for SauceConnect
+        pidfile="/tmp/.sauceconnect_$SE_PORT.pid"
+        exec /usr/local/bin/sc \
+                --logfile - \
+                --user "$SAUCE_USERNAME" \
+                --api-key "$SAUCE_ACCESS_KEY" \
+                --pidfile "$pidfile" \
+                --se-port "$SE_PORT" \
+                --no-remove-colliding-tunnels \
+                --wait-tunnel-shutdown
+end script
+
+# Remove PID file once we've started the service since it's not needed
+post-start exec rm -f "/tmp/.sauceconnect_$SE_PORT.pid"

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: blade-sauce_labs_plugin
 version: !ruby/object:Gem::Version
-  version: 0.5.2
+  version: 0.5.3
 platform: ruby
 authors:
 - Javan Makhmali
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2016-06-04 00:00:00.000000000 Z
+date: 2016-08-22 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler
@@ -135,6 +135,12 @@ files:
 - lib/blade/sauce_labs_plugin/version.rb
 - lib/blade/sauce_labs_plugin/web_driver.rb
 - support/sc-linux/bin/sc
+- support/sc-linux/config/systemd/README.md
+- support/sc-linux/config/systemd/sc.service
+- support/sc-linux/config/systemd/sc@.service
+- support/sc-linux/config/upstart/README.md
+- support/sc-linux/config/upstart/sc.conf
+- support/sc-linux/config/upstart/sc_worker.conf
 - support/sc-linux/include/sauceconnect.h
 - support/sc-linux/lib/libsauceconnect.a
 - support/sc-linux/lib/libsauceconnect.la
@@ -142,6 +148,12 @@ files:
 - support/sc-osx/bin/sc
 - support/sc-osx/bin/sc.dSYM/Contents/Info.plist
 - support/sc-osx/bin/sc.dSYM/Contents/Resources/DWARF/sc
+- support/sc-osx/config/systemd/README.md
+- support/sc-osx/config/systemd/sc.service
+- support/sc-osx/config/systemd/sc@.service
+- support/sc-osx/config/upstart/README.md
+- support/sc-osx/config/upstart/sc.conf
+- support/sc-osx/config/upstart/sc_worker.conf
 - support/sc-osx/include/sauceconnect.h
 - support/sc-osx/lib/libsauceconnect.a
 - support/sc-osx/lib/libsauceconnect.la
@@ -166,7 +178,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.5.1
+rubygems_version: 2.6.6
 signing_key: 
 specification_version: 4
 summary: Blade Runner plugin for Sauce Labs (saucelabs.com)