You can find the complete changelog for each version of the Jenkins Plugin at GitHub: https://github.com/saucelabs/jenkins-sauce-ondemand-plugin/blob/master/CHANGELOG.md
ondemand.saucelabs.comfrom your Jenkins server. Check out the Jenkins documentation if you need to set up a proxy or other advanced network configuration.
You can install the Sauce OnDemand plugin for Jenkins though the Jenkins Administration page.
The Jenkins plugin provides an interface for storing your Sauce Labs authentication credentials as environment variables on the Jenkins server, which is one of our best practices for testing with Sauce. This allows you to reference your credentials without having to hardcode them into your tests, and because the plugin manages authentication at the global level, you can have multiple jobs running at the same time that use these credentials.
You can click an existing domain or click Add domain.
You can now use these credentials on a per project basis. To do so:
Under Sauce Labs Options, you will see the credentials you have stored as an option under Credentials.
You can also add credentials here on the fly.
In versions of the plugin prior to 1.147 credential management is handled slightly differently. For older versions of the plugin you will find credential management in the Manage Jenkins > Configure System section:
Once you've set up your authentication credentials as environment variables, you can refer to them in your tests like this:
Check out the topic Setting Desired Capabilities for Jenkins Projects for more information about using environment variables.