We sponsored the Jenkins World Conference last month, Aug 28-31, in San Francisco and it was an eye-opener. As the developer of CBT’s Jenkins plugin, I was asked to attend the conference to ‘man the booth’. Many people that came by asked me if the Crossbrowsertesting.com Jenkins plugin supported Jenkins Pipeline. At the time, the only answer I could give them was “not currently, but it will”. Prior to attending the conference, I was unaware of the volume of users using Pipeline, and I did not have a lot of personal experience with the pipelining capability. That has changed! We are now introducing support for Jenkins Pipelining in our plugin.
Jenkins Pipeline is an automated expression of your process for getting software from version control right through to your users. Every change to your software goes through a complex process on its way to being released (ie. Build, Test, Deploy) and Pipeline supports scripting this repeatable process (in a file called a “Jenkinsfile”). You can then check this script in your version control repository and Jenkins will run it as a build configuration. Jenkins Pipeline also features a Pipeline Syntax GUI that automatically generates code snippets for you to copy and paste into you pipeline script.
As of version 2.3 of the Crossbrowsertesting.com Jenkins Plugin, you can now script:
- Running Selenium Scripts on Crossbrowsertesting.com
- Running Automated Screenshots Tests on Crossbrowsertesting.com
- Automated starting and stopping of the Crossbrowsertsting.com NodeJS local tunnel to test local and development webpages behind your firewall
- Enabling Test Results Views with links to download Screenshots for Screenshots Testing and view videos and packet captures for Selenium Tests
After attending the conference, not only did I immediately start working towards adding support for the plugin, but I also began making changes to the Jenkins Server configuration running in our own development environment. “Jenkinsfile” configurations will completely revolutionize configuring our Jenkins jobs with its scripting and ease of use.
So now, we have full integration with Jenkins Pipeline, and if you’d like to try it out, you can check the links below: