The official Sauce Labs Blog
Posts Tagged ‘Bamboo’
In case you missed the Bamboo webinar yesterday, here’s a short video that walks you through integrating Bamboo with Sauce OnDemand. Thanks to Jonathan Doklovic and Systems Bliss for creating the Bamboo Sauce Plugin (available for download here), and for providing us with a great tutorial!
The Sauce Labs ecosystem continues to happily grow with the addition of a new CI plugin built specifically for Sauce OnDemand.
Bamboo Sauce, created by Systems Bliss engineer Jonathan Doklovic, enables Bamboo users to easily integrate with Sauce OnDemand to run builds across multiple browsers in parallel. Sign up for the live demo this Thursday at 11 am PST to see how this pairing will speed up your test cycles and reduce the need for costly test infrastructure, while leveraging your existing investment in Bamboo, the popular Atlassian CI server.
Setup is simple, needing only a one-time admin configuration, and builds can be customized to test on a variety of OS/Browser combinations. Bamboo Sauce takes care of Firewall problems by creating a direct SSH tunnel from the cloud to a specific server (when you use Sauce OnDemand, we never see your code – rather, it stays behind whatever guard you have in place), and it also lets you pick which tests you want recorded via Sauce TV.
To find out more, tune in to the live demo, led by Systems Bliss and Sauce Labs. Jonathan of Sysbliss will walk you through setting up Bamboo Sauce, and also answer any questions. To follow along step-by-step, download the plugin and sign up for a free 30 day trial of Sauce OnDemand.
(To note – Bamboo Sauce is still in beta. We’d love to hear any feedback you have, so please let us know!)
Testing is a key ingredient in CI. And so in the constant effort to make our service insanely flexible and easy to use, we’ve released a brand new API that will help Continuous Integration servers such as Hudson, Bamboo, and TeamCity send Sauce OnDemand some interesting information about each test they run.
This includes the pass/fail final status of the test, the build number in which it was run, and even your own custom data.
Since some of this new job info is known only when the test finishes (e.g. whether the job passed or not), we’ve created not only one but two alternative methods for the info to be sent – the REST API and Selenium’s standard setContext command. Both are documented in our docs, and anyone interested can use them right now.
Once the info makes it to our end, it will be appropriately displayed with each job, helping our users find and group their jobs with less effort. (Notice that some of the work needed to display this in a cool way is still in our TODO – but the data is there). You can see some example jobs [1] with this data set or just create your own!
In the near future, we’ll be working with the authors of the Hudson and Bamboo plugins to add support for these CI APIs.
If you’re interested in hearing more, trying early versions of these plugins, or would like to see a plugin for another CI system, feel free to ping us here!
[1] https://saucelabs.com/jobs/4baf3ad0cd8b686ef554135c4addf621,
https://saucelabs.com/jobs/0d925d14c23888b8561215360b70a78d
