Become a JMeter and Continuous Testing Pro

Start Learning

Test Your Website Performance NOW!

arrow Please enter a URL with http(s)
Jun 18 2013

Load Testing: Using Jenkins Continuous Integration in the Cloud

Software development is no simple matter these days, what with ever more complex apps and bigger demands on them. There are a whole load of tasks that must be taken into consideration to ensure that software is developed successfully. Beside s the actual development itself, there’s testing, debugging, the deployment into production and (while we hope not) more debugging. It can be an onerous process.

Additionally, quality control is imperative. It’s no good implementing all of these tasks if the end result remains unsatisfactory. That’s why the best developers use continuous integration (CI).

CI servers help developers ensure that they can clearly identify bugs, bottlenecks and system failures, so they can fix them swiftly and be confident that their software is robust.  

Developers can choose to use a variety of CI servers. Jenkins is one of the most popular. But basically, if CI is what is needed, developers only have a couple of options. Either configure your own server or use a cloud solution. The latter is usually the easier and preferred option.

CloudBees is a Java meets the Cloud, so it offers an ideal solution by combining the two. Plus, it now includes BlazeMeter’s load testing cloud. As a result, CloudBees makes continuous integration simpler and more efficient than ever. And it’s no longer necessary to set up a separate Jenkins server.

BlazeMeter’s platform for building applications and running performance tests is the best choice for developers that want to use Jenkins. And it’s simple and fast to use it. Simply log on to your CloudBees account, and go to your dashboard , where you’ll find all the possible options to maximize your CI.

Lil' bit of instruction:
After you've logged into your CloudBees account, head into your dashboard which contains all possible options.
Login to the CloudBees Platform
Select Jenkins
Select Jenkins from the CloudBees Platform
Go to Manage Jenkins section.
Select Manage Jenkins
Now select Configure System.
Configure your system
Scroll down -> Blazemeter Cloud section and type your Blazemeter userkey (in your BlazeMeter account profile. If you don’t have one sign up for a free account)
BlazeMeter userkey
Save and go the main menu where you can create the new job and enter a job name as usual. Then scroll to Post-build Actions and add BlazeMeter task.
Add BlazeMeter task
Enter all the information and save it and run. 
Add data to post build actions after selecting BlazeMeter
If there are no other post-build steps, then the system will deal with the Blazemeter test immediately. Once complete go to this specific build and switch to BlazeMeter Report.
Get your BlazeMeter report after build run on CloudBees
Once the run is complete- you will see the results in your BlazeMeter report.
BlazeMeter Reporting Results on CloudBees
With BlazeMeter and CloudBees now fully integrated cloud platforms developers are "free" from tasks such as configuring Jenkins or load testing environments, procuring resources in advance or any other actions that take up far too much valuable time. The integrations allows developers and devops to spend more time developing and ensuring failure resilient applications vs spending vast amounts of time configuring testing environments et al.
arrow Please enter a URL with http(s)

You might also find these useful:

Interested in writing for our Blog?Send us a pitch!