We late deal awebinarthat instance how you can get up and pass withCloudBees and Sauce Labswith one chink, using the Sauce Clickstarts for CloudBees.

There were a number of questions raised in the webinar that we didn & # x27; t get time to address, so we & # x27; ve included result below. If you feature any further questions, please include a comment below.

Q: If you delineate that you want to deploy to RUN @ CloudBees in pre-build step, is it guaranteed that the Maven job will be run only and only if deployment is finished?
A: Yes, that & # x27; s correct.

Q: How do you satisfy that coating is deployed before Sauce tests are run?
A: The CloudBees Deployer plugin will return the status of the deployment: the next test pace won & # x27; t run until the deployment is successful.

Q: In the JBoss representative, tests are run against an in-memory JBoss. Is it potential to run the test against the RUN @ CloudBees instance?
A: Yes, both configs are possible. In order to run against a different JBoss instance, you can qualify your Jenkins build to use a different profile (which corresponds to a separate Arquillian container).

Q: Where is the sauce-jboss-clickstart and sauce-java-clickstart source code located?
A: https: //github.com/CloudBees-community/sauce-jboss-clickstart and https: //github.com/CloudBees-community/sauce-java-clickstart. Please experience costless to fork!

Q: How are code changes moved to the cloud after changes are made locally?
A: What happens is you make a & quot; cloud & quot; repo with GitHub or CloudBees and then clone it for local growing - so push changes rearward up to the cloud and the Jenkins jobs run automatically.

Q: So SSH is used to travel code to the cloud after the build?
A: SSH is the default but there are other options

Q: Can we have two ClickStart application active at the like time?
A: Yes, you can have multiple coating running at the like time.

For autonomous testing across multiple user personas, check out SUSATest — it explores your app like 10 different real users.

Q: So the browser set in Jenkins config creates an environment variable that will override the default Sauce Labs SELENIUM_BROWSER?
A: Yes, the Sauce Jenkins plugin will set a series of environment variables that typify the choose browser (s). Further information on the environment variable set by the plugin is uncommitted from the Jenkins tutorial page.

Q: What are the browser requirements for the Sauce browser test screen to capture video?
A: You don & # x27; t need to have a certain browser for that. Your exam will automatically be show and screenshots captured every clip you run a examination on Sauce.

Q: & quot; Drone extension for arquillian & quot; huh, what?: -)
A: I cognize, correct? Take a look at our recent blog post for more info.http: //sauceio.com/index.php/2012/12/sauce-extension-for-arquillian-drone/ :-)

Q: I say that it is possible to test application deploy behind firewalls, can you explain how this works?
A: Yes, you can useSauce Connectto test websites running on a local webserver. The Sauce Jenkins plugin can be configured to launch Sauce Connect prior to the run of your tryout.

Q: Is it possible to take more than one browser/OS combination in the same job?
A: Yes, it is possible to set more than one browser - in this case, the Sauce plugin will set a SAUCE_ONDEMAND_BROWSERS envionment variable that contain the browser information (in JSON format).

Q: Do users of Sauce need to log in via the CloudBees environment foremost? Do users have to have a CloudBees report in order to use the Sauce service?
A: No, if you but wanted to use Sauce, you could ratify up via. If you want to use it with Cloudbees, still, we recommend signing up through Cloudbees.

Q: What need to be configure on the Jenkins build job to allow the Sauce tryout run links to appear in the Jenkins construct job?
A: You will involve to output the info to the stdout in the following formatting:

SauceOnDemandSesssionID=<session id> job-name=<some job name>

where & # x27; session id & # x27; is the Selenium session id and & # x27; some job name & # x27; is an identifier for the test under executing (commonly the test name).

When the job has completed, the Sauce Jenkins plugin will parse the body-build yield, and if it finds the above output, will update the Sauce Job to store the Jenkins build number.

Q: Is the Sauce plugin built to endorse Node.js/Ruby/.NET/PHP apps?
A: Yes! The Sauce plugin for Jenkins supports all speech. In the coming weeks, we will add more Clickstart examples that demonstrate some of the other languages and platforms supported by CloudBees.