blade-sauce_labs_plugin 0.7.2 → 0.7.3
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +5 -5
- data/lib/blade/sauce_labs_plugin/version.rb +1 -1
- data/support/sc-linux/bin/sc +0 -0
- data/support/sc-linux/config_examples/systemd/README.md +12 -6
- data/support/sc-linux/config_examples/systemd/sc@.service +2 -3
- data/support/sc-linux/config_examples/upstart/README.md +11 -4
- data/support/sc-linux/config_examples/upstart/sc_worker.conf +1 -2
- data/support/sc-osx/bin/sc +0 -0
- data/support/sc-osx/config_examples/systemd/README.md +12 -6
- data/support/sc-osx/config_examples/systemd/sc@.service +2 -3
- data/support/sc-osx/config_examples/upstart/README.md +11 -4
- data/support/sc-osx/config_examples/upstart/sc_worker.conf +1 -2
- metadata +3 -3
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
|
-
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
2
|
+
SHA256:
|
|
3
|
+
metadata.gz: 2bd5b75b9709212b65a9dbeba598abd0a2dd22d906b673ca87de272d8f65b19d
|
|
4
|
+
data.tar.gz: 22b36e075c8adb98af9178bd12ad82423a524a6fb2e63ddff37c46104bc036c0
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: f00e1bdfdbff728185be9c4147810c3d3eb01d31a05864f2454f00f5e2adfd3d2d47cf87b76ed7d4d8547e65dbae87742545aaf5e6bf7ab5cddd4162a2450f72
|
|
7
|
+
data.tar.gz: 45b584517d2e08cd023cf74deeb94f4dab7d6bbf3bcf35f18ae84a2210e2c951c40b3982b53ebf9cae6c52ddc252f7cc0d216ed3bae744839b881a1273997126
|
data/support/sc-linux/bin/sc
CHANGED
|
Binary file
|
|
@@ -1,16 +1,22 @@
|
|
|
1
1
|
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/
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
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.
|
|
4
4
|
|
|
5
|
-
|
|
5
|
+
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 your local machine or behind a firewall. For more information check out the Sauce Labs documentation wiki: https://wiki.saucelabs.com/display/DOCS/Sauce+Connect+Proxy
|
|
6
6
|
|
|
7
|
-
|
|
7
|
+
These instructions will show you how to set up systemd with Sauce Connect to manage the starting and stopping of Sauce Connect tunnels.
|
|
8
8
|
|
|
9
9
|
Setting Up systemd
|
|
10
10
|
----------------
|
|
11
11
|
|
|
12
|
-
1.
|
|
13
|
-
2.
|
|
12
|
+
1. Install the Sauce connect binary in `bin/sc` to `/usr/local/bin/sc`.
|
|
13
|
+
2. Set permissions on Sauce connect binary with `chown nobody: /usr/local/bin/sc`
|
|
14
|
+
3. Copy the files `sc.service` & `sc@.service` to `/etc/systemd/system`.
|
|
15
|
+
4. Review and update example service files for your system. For example:
|
|
16
|
+
* Set `SAUCE_USERNAME` and `SAUCE_ACCESS_KEY` environment variables
|
|
17
|
+
* Confirm correct group for user `nobody`
|
|
18
|
+
* Confirm the command run by `ExecStart` works when run manually on your system.
|
|
19
|
+
5. Create a directory `sc.service.wants` in `/etc/systemd/system`.
|
|
14
20
|
You'll have to create symbolic links inside this directory to set up new instances of Sauce
|
|
15
21
|
Connect. For example, if you'd like to have two Sauce Connect instances listening on
|
|
16
22
|
port 8000 & 8001:
|
|
@@ -20,7 +26,7 @@ port 8000 & 8001:
|
|
|
20
26
|
$ sudo ln -s /etc/systemd/system/sc@.service ./sc.service.wants/sc@8000.service
|
|
21
27
|
$ sudo ln -s /etc/systemd/system/sc@.service ./sc.service.wants/sc@8001.service
|
|
22
28
|
```
|
|
23
|
-
|
|
29
|
+
6. Add your Saucelabs credentials to `/etc/systemd/system/sc@.service` in the
|
|
24
30
|
service section like this:
|
|
25
31
|
```
|
|
26
32
|
Environment=SAUCE_USERNAME=myusername
|
|
@@ -6,7 +6,7 @@ ReloadPropagatedFrom=sc.service
|
|
|
6
6
|
[Service]
|
|
7
7
|
Type=simple
|
|
8
8
|
User=nobody
|
|
9
|
-
Group=
|
|
9
|
+
Group=nobody
|
|
10
10
|
WorkingDirectory=/tmp
|
|
11
11
|
LimitNOFILE=8192
|
|
12
12
|
Restart=always
|
|
@@ -19,8 +19,7 @@ ReloadPropagatedFrom=sc.service
|
|
|
19
19
|
--logfile - \
|
|
20
20
|
--pidfile "/tmp/sauceconnect_%i.pid" \
|
|
21
21
|
--se-port "%i" \
|
|
22
|
-
--no-remove-colliding-tunnels
|
|
23
|
-
--wait-tunnel-shutdown
|
|
22
|
+
--no-remove-colliding-tunnels
|
|
24
23
|
# Not needed with systemd
|
|
25
24
|
ExecStartPost = /bin/rm -f /tmp/sauceconnect_%i.pid
|
|
26
25
|
|
|
@@ -2,20 +2,27 @@ Upstart is an event-based replacement for the `/sbin/init` Linux daemon that han
|
|
|
2
2
|
|
|
3
3
|
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.
|
|
4
4
|
|
|
5
|
-
Sauce Connect is a secure tunneling application that
|
|
5
|
+
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 your local machine or behind a firewall. For more information check out the Sauce Labs documentation wiki: https://wiki.saucelabs.com/display/DOCS/Sauce+Connect+Proxy
|
|
6
6
|
|
|
7
7
|
These instructions will help you set up Sauce Connect so that the starting and stopping of tunnels is controlled by Upstart.
|
|
8
8
|
|
|
9
|
-
|
|
9
|
+
Setting Up Upstart
|
|
10
|
+
------------------
|
|
11
|
+
|
|
12
|
+
1. Install the Sauce connect binary in `bin/sc` to `/usr/local/bin/sc`.
|
|
10
13
|
2. Copy the `sc_worker.conf` & `sc.conf` files to `/etc/init`.
|
|
11
14
|
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.
|
|
12
|
-
3.
|
|
15
|
+
3. Review and update example service files for your system. For example:
|
|
16
|
+
* Set `SAUCE_USERNAME` and `SAUCE_ACCESS_KEY` environment variables
|
|
17
|
+
* Confirm correct group for user `nobody`
|
|
18
|
+
* Confirm the `sc` command works when run manually on your system.
|
|
19
|
+
4. Check that the services are installed correctly with the `initctl list` command:
|
|
13
20
|
```
|
|
14
21
|
$ initctl list | grep '^sc'
|
|
15
22
|
sc_worker stop/waiting
|
|
16
23
|
sc stop/waiting
|
|
17
24
|
```
|
|
18
|
-
|
|
25
|
+
5. Create a file named `/etc/default/sc` to store Sauce Connect's configuration options.
|
|
19
26
|
It should look something like that:
|
|
20
27
|
```
|
|
21
28
|
SAUCE_USERNAME=username
|
|
@@ -51,8 +51,7 @@ script
|
|
|
51
51
|
--logfile - \
|
|
52
52
|
--pidfile "$pidfile" \
|
|
53
53
|
--se-port "$SE_PORT" \
|
|
54
|
-
--no-remove-colliding-tunnels
|
|
55
|
-
--wait-tunnel-shutdown
|
|
54
|
+
--no-remove-colliding-tunnels
|
|
56
55
|
end script
|
|
57
56
|
|
|
58
57
|
# Remove PID file once we've started the service since it's not needed
|
data/support/sc-osx/bin/sc
CHANGED
|
Binary file
|
|
@@ -1,16 +1,22 @@
|
|
|
1
1
|
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/
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
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.
|
|
4
4
|
|
|
5
|
-
|
|
5
|
+
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 your local machine or behind a firewall. For more information check out the Sauce Labs documentation wiki: https://wiki.saucelabs.com/display/DOCS/Sauce+Connect+Proxy
|
|
6
6
|
|
|
7
|
-
|
|
7
|
+
These instructions will show you how to set up systemd with Sauce Connect to manage the starting and stopping of Sauce Connect tunnels.
|
|
8
8
|
|
|
9
9
|
Setting Up systemd
|
|
10
10
|
----------------
|
|
11
11
|
|
|
12
|
-
1.
|
|
13
|
-
2.
|
|
12
|
+
1. Install the Sauce connect binary in `bin/sc` to `/usr/local/bin/sc`.
|
|
13
|
+
2. Set permissions on Sauce connect binary with `chown nobody: /usr/local/bin/sc`
|
|
14
|
+
3. Copy the files `sc.service` & `sc@.service` to `/etc/systemd/system`.
|
|
15
|
+
4. Review and update example service files for your system. For example:
|
|
16
|
+
* Set `SAUCE_USERNAME` and `SAUCE_ACCESS_KEY` environment variables
|
|
17
|
+
* Confirm correct group for user `nobody`
|
|
18
|
+
* Confirm the command run by `ExecStart` works when run manually on your system.
|
|
19
|
+
5. Create a directory `sc.service.wants` in `/etc/systemd/system`.
|
|
14
20
|
You'll have to create symbolic links inside this directory to set up new instances of Sauce
|
|
15
21
|
Connect. For example, if you'd like to have two Sauce Connect instances listening on
|
|
16
22
|
port 8000 & 8001:
|
|
@@ -20,7 +26,7 @@ port 8000 & 8001:
|
|
|
20
26
|
$ sudo ln -s /etc/systemd/system/sc@.service ./sc.service.wants/sc@8000.service
|
|
21
27
|
$ sudo ln -s /etc/systemd/system/sc@.service ./sc.service.wants/sc@8001.service
|
|
22
28
|
```
|
|
23
|
-
|
|
29
|
+
6. Add your Saucelabs credentials to `/etc/systemd/system/sc@.service` in the
|
|
24
30
|
service section like this:
|
|
25
31
|
```
|
|
26
32
|
Environment=SAUCE_USERNAME=myusername
|
|
@@ -6,7 +6,7 @@ ReloadPropagatedFrom=sc.service
|
|
|
6
6
|
[Service]
|
|
7
7
|
Type=simple
|
|
8
8
|
User=nobody
|
|
9
|
-
Group=
|
|
9
|
+
Group=nobody
|
|
10
10
|
WorkingDirectory=/tmp
|
|
11
11
|
LimitNOFILE=8192
|
|
12
12
|
Restart=always
|
|
@@ -19,8 +19,7 @@ ReloadPropagatedFrom=sc.service
|
|
|
19
19
|
--logfile - \
|
|
20
20
|
--pidfile "/tmp/sauceconnect_%i.pid" \
|
|
21
21
|
--se-port "%i" \
|
|
22
|
-
--no-remove-colliding-tunnels
|
|
23
|
-
--wait-tunnel-shutdown
|
|
22
|
+
--no-remove-colliding-tunnels
|
|
24
23
|
# Not needed with systemd
|
|
25
24
|
ExecStartPost = /bin/rm -f /tmp/sauceconnect_%i.pid
|
|
26
25
|
|
|
@@ -2,20 +2,27 @@ Upstart is an event-based replacement for the `/sbin/init` Linux daemon that han
|
|
|
2
2
|
|
|
3
3
|
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.
|
|
4
4
|
|
|
5
|
-
Sauce Connect is a secure tunneling application that
|
|
5
|
+
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 your local machine or behind a firewall. For more information check out the Sauce Labs documentation wiki: https://wiki.saucelabs.com/display/DOCS/Sauce+Connect+Proxy
|
|
6
6
|
|
|
7
7
|
These instructions will help you set up Sauce Connect so that the starting and stopping of tunnels is controlled by Upstart.
|
|
8
8
|
|
|
9
|
-
|
|
9
|
+
Setting Up Upstart
|
|
10
|
+
------------------
|
|
11
|
+
|
|
12
|
+
1. Install the Sauce connect binary in `bin/sc` to `/usr/local/bin/sc`.
|
|
10
13
|
2. Copy the `sc_worker.conf` & `sc.conf` files to `/etc/init`.
|
|
11
14
|
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.
|
|
12
|
-
3.
|
|
15
|
+
3. Review and update example service files for your system. For example:
|
|
16
|
+
* Set `SAUCE_USERNAME` and `SAUCE_ACCESS_KEY` environment variables
|
|
17
|
+
* Confirm correct group for user `nobody`
|
|
18
|
+
* Confirm the `sc` command works when run manually on your system.
|
|
19
|
+
4. Check that the services are installed correctly with the `initctl list` command:
|
|
13
20
|
```
|
|
14
21
|
$ initctl list | grep '^sc'
|
|
15
22
|
sc_worker stop/waiting
|
|
16
23
|
sc stop/waiting
|
|
17
24
|
```
|
|
18
|
-
|
|
25
|
+
5. Create a file named `/etc/default/sc` to store Sauce Connect's configuration options.
|
|
19
26
|
It should look something like that:
|
|
20
27
|
```
|
|
21
28
|
SAUCE_USERNAME=username
|
|
@@ -51,8 +51,7 @@ script
|
|
|
51
51
|
--logfile - \
|
|
52
52
|
--pidfile "$pidfile" \
|
|
53
53
|
--se-port "$SE_PORT" \
|
|
54
|
-
--no-remove-colliding-tunnels
|
|
55
|
-
--wait-tunnel-shutdown
|
|
54
|
+
--no-remove-colliding-tunnels
|
|
56
55
|
end script
|
|
57
56
|
|
|
58
57
|
# Remove PID file once we've started the service since it's not needed
|
metadata
CHANGED
|
@@ -1,14 +1,14 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: blade-sauce_labs_plugin
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 0.7.
|
|
4
|
+
version: 0.7.3
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- Javan Makhmali
|
|
8
8
|
autorequire:
|
|
9
9
|
bindir: exe
|
|
10
10
|
cert_chain: []
|
|
11
|
-
date:
|
|
11
|
+
date: 2018-05-09 00:00:00.000000000 Z
|
|
12
12
|
dependencies:
|
|
13
13
|
- !ruby/object:Gem::Dependency
|
|
14
14
|
name: bundler
|
|
@@ -192,7 +192,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
|
|
|
192
192
|
version: '0'
|
|
193
193
|
requirements: []
|
|
194
194
|
rubyforge_project:
|
|
195
|
-
rubygems_version: 2.
|
|
195
|
+
rubygems_version: 2.7.6
|
|
196
196
|
signing_key:
|
|
197
197
|
specification_version: 4
|
|
198
198
|
summary: Blade Runner plugin for Sauce Labs (saucelabs.com)
|