Configuration

After installing a plugin, specify your Sauce Labs access credentials in the system configuration page as follows:

Once this is set, on each job configuration page, you can tell Jenkins to launch a Sauce Connect instance for the duration of the build. For more details about the concept of SSH tunnel in the context of Sauce Labs, see the documentation.

Embedded Test Reports

You can show an embedded Sauce Labs test report on the test result pages in Jenkins. To enable this, check 'Embed Sauce OnDemand reports' as part of the 'Publish JUnit test result report section'.

In addition, you will need to output the following line to your for each test that is run using Sauce Labs:

SauceOnDemandSessionID=YOUR_SESSION_ID job-name=YOUR_JOB_NAME

where YOUR_SESSION_ID is the SeleniumRC/WebDriver session id and YOUR_JOB_NAME is the name of the test being executed.

Issue Tracking

Please raise any issues you find with the plugin or requests for additional features within the plugin's Jira instance.

Changelog

Version 1.123

Support supplying the path to an existing Sauce Connect installation, and include Sauce Connect 4.3.8

Version 1.122

Resolve NullPointerException when processing results with no test data

Version 1.121

Process stdout lines when no test publisher has been defined

Version 1.120

Use Sauce Connect 4.3.7

Version 1.119

Resolve NullPointerException in result parsing

Version 1.118

Include fix for JENKINS-25236

Version 1.117

Lock startup of Sauce Connect based on tunnel identifier

Version 1.116

Add ability to specify a prefix for the SELENIUM_* environment variables, fix JENKINS-26662

Version 1.115

Include 32-bit Linux Sauce Connect

Version 1.114

Query Sauce REST API to see if there are any active tunnels before launching new tunnel

Version 1.104

Version 1.103

Version 1.102

Supply browser's long name as part of SAUCE_ONDEMAND_BROWSERS environment variable

Version 1.101

Supply short and long version in SAUCE_ONDEMAND_BROWSERS environment variable

Version 1.100

Support retrieving latest version of browser

Version 1.99

Support portrait and landscape device orientation

Version 1.97

Removed sauceConnectHandler instance variable

Version 1.93

The plugin will treat Sauce Connect startup timeouts as errors, which will cause the build to fail (previously these errors were only being logged). Verbose logging of Sauce Connect is now enabled by default.

Version 1.92

Updated plugin to use Sauce Connect version 4.3

Version 1.90

Use the Suite Result stdout and stderr in addition to the Case Result

Version 1.89

Added a 'Verbose logging' option to the Job Configuration page, which will enabled the Sauce Connect output to be included with the job console output

Version 1.88

Fix issue with selection of 'Use Sauce Connect v3' option not saving

Version 1.87

The default behaviour of launching Sauce Connect is now to launch on the Slave node instead of the Master node.

Version 1.86

Recompiled linux build of Sauce Connect

Version 1.85

Updated plugin to use Sauce Connect version 4.2

Version 1.84

Use correct directory for Sauce Connect running under Windows

Version 1.83

Use Jenkins proxy information to retrieve list of supported browsers from Sauce Labs

Version 1.80

Use latest version of Sauce Connect (both v4 and v3)

Version 1.74

Add support for Sauce Connect version 4

Version 1.68

Use Jenkins proxy settings when retrieving list of supported browsers from Sauce Labs

Version 1.67

Only display the Sauce badge for the applicable build. Set the pass/fail status based on the test result, not the Jenkins build

Version 1.15

Version 1.14

Version 1.13

Version 1.12

Set the working directory when invoking Sauce Connect. The working directory can be set via the Adminstration interface, and will default to the user home directory if not set.

Version 1.11

Updated plugin to provide better support for multi-configuration jobs. The plugin will now launch a single instance of Sauce Connect per user. That is, if a multi-configuration Job is configured to run using multiple browsers, then only one Sauce Connect instance will be launched for the Jobs.

The plugin now also allows the user to specify the browser(s) to be used on the Job level. If multiple browsers are selected, then they will be included in JSON format in a SAUCE_ONDEMAND_BROWSERS environment variable

Hey Mike, I hope you figured out the Issue by now. I just ran into the sam...

Hey Mike, I hope you figured out the Issue by now. I just ran into the same problem but wanted to post my solution for others (Google didn't seem to have the answer). I just downloaded the jackson (http://jackson.codehaus.org/) jar (all) from http://wiki.fasterxml.com/JacksonDownload and copied it into plugins/sauce-ondemand/WEB-INF/lib/. Then just restarted Jenkins and the test button worked.

I just updated my plugin to v1.8 (jenkins v1.448) and all of the sauce-on-demand...

I just updated my plugin to v1.8 (jenkins v1.448) and all of the sauce-on-demand browser options in the matrix configuration are missing - the checkboxes are there but there are no values. Anyone else experience this? I've reverted back to v1.4 and then tried applying the update to 1.8 again, with no luck.