The LoadView Plugin for Jenkins

Add LoadView tests to your Jenkins Builds


Discover performance issues earlier and release more reliable applications to production by integrating LoadView performance tests into your CI development process. Generate comprehensive test reports and gain insights into code performance.

Jenkins: Open-source Automation and Continuous Integration


Before we dive into the specifics of the LoadView Plugin for Jenkins, we’ll discuss Jenkins and why is it important.

Jenkins is an open-source automation server built on the Java Virtual Machine (JVM), supporting thousands of plugins for the development, deployment, and automation of software projects. They are the leader in the open-source automation server space. Other companies that provide open-source automation servers are TeamCity, CircleCI, Hudson, Travis CI, Atlassian Bamboo, among many others.

As part of modern software delivery practices, such as shift left testing and continuous integration, developers, testers, and designers all utilize Jenkins to build, deploy, and automate their tests.  Over time, as development and testing cycles became shorter and more frequent due to technological advances and the focus on the digital experience, it became apparent that in order to release quality software features – and consistently – teams as a whole needed to become more agile. This meant that testing now “shifted” to the left and happened earlier, typically after the initial code is written. This “test early and often” mantra is especially significant in continuous integration and continuous delivery (CI/CD), where the goal is to be able to consistently and continually release changes.

Read more about shift left testing and load testing best practices for DevOps

Continuous integration essentially ditches the need to test from one’s own machine and automatically test every time new code is pushed into shared source repository, which could be multiple time per day. The advantage of continuous integration is that all development work and code can be integrated into the process earlier, helping to identify and fix bugs or errors more quickly and effectively. The quicker you can find and fix software errors, the more likely you won’t have to fix it in production, where it can be more time consuming and expensive.

To extend continuous integration further, teams use continuous delivery practices to automate and control the software release cycles on top of automating the software testing process. Furthermore, teams can employ continuous deployment, which essentially removes the need for almost any human involvement. All changes that pass through your software development stages are automatically released into production.

What is CI/CD?

Continuous integration (CI) and continuous delivery (CD) epitomize a culture, set of operating principles, and collection of practices that allow application development teams to deliver code changes more frequently and reliably. This is known as CI/CD pipeline.  CI/CD is one of the best practices for DevOps teams to adopt. It is also an agile methodology best practice, as it allows software development teams to focus on meeting business prerequisites, code quality, and security as deployment steps are automated.


The Difference Between CI and CD

It’s unclear how this conflation of the two terms started. Be that as it may, it’s sufficiently simple to clear up.


Continuous Integration

Continuous integration is the way toward coordinating code into a mainline code base. In practically all situations today, continuous integration is finished utilizing stages that are structured explicitly for a reason. Executing continuous integration is, in this manner, is as necessary as utilizing the correct tools.


Continuous Delivery

Continuous delivery, on the other hand, essentially sets out to automate the entire software testing cycle and trying to remove as much manual work as possible, which allows developers the time to work on other projects and not have to manage all the individual steps.


Benefits of CI/CD
  • Smaller code changes are less complicated (increasingly nuclear) and have less unintended outcomes
  • Deficiency disconnection is less complicated and faster
  • Interim to the goal, mean time to repair (MTTR), is shorter due to the smaller code changes and faster shortcoming disengagement
  • Testability improves because of smaller, explicit changes. These little changes permit increasingly exact positive and negative tests
  • Passed time to distinguish and address creation escapes is shorter, with a quicker pace of discharge
  • The build-up of non-basic deformities is lower and frequently fixed before other component issues emerge
  • Redesigns present smaller units of progress and are less troublesome


CI/CD Uses & Implementation

CI/CD is many strategies that empower application designers to convey code changes all the more much of the time to clients using computerization.

The abbreviation CI/CD alludes to two separate ideas that are commonly utilized together: ceaseless mix and consistent conveyance.  Ceaseless coordination alludes to a mechanization procedure that engineers use to fabricate, test, and combine application code changes.  Persistent conveyance is the subsequent stage in which the tried code from the ceaseless mix is naturally sent in different situations by a manual trigger.  Continuous delivery can likewise represent the ceaseless arrangement, which presents further computerization. In nonstop conveyance, engineers need to push changes to their creation condition physically. By utilizing nonstop organization rather, designers can have application changes consequently sent to any condition. For this conversation, we will just concentrate on the ideas of ceaseless mix and consistent conveyance.


How CI/CD Works

The cutting edge, relentless universe of user improvement requests that various engineers take a shot during a single application happen all the time. When designers are prepared to test their changes in a standard life cycle, they consolidate their code changes on a preordained “combine day.” The blending procedure can be tedious and time-consuming. It turns out to be much more complex if a designer’s change influences another engineer’s change, at last driving the group to rollback or go through hours on bug fixes.


The Continuous Integration Phase

Changing over to a CI/CD process helps designers combine and test code all the more as often as possible, even every day.  The nonstop joining stage follows these fundamental steps:

  • A designer takes code from the collective archive to chip away at it, perhaps making another branch for another element.
  • When the new element is finished, the engineer pushes it back to the typical vault.
  • The CI engineer confirms that changes have been made and starts to fabricate and tests the application, guaranteeing that the progressions have not made the application break. The tests center around all out usefulness to guarantee that no piece of the application has been undermined.
  • The advancement group is informed of the test outcomes. In the case of disappointment, the group will realize that the new code has caused disappointment and can start to seclude and fix the issue. If the progressions are active, the group proceeds onward to the ceaseless conveyance stage.


The Continuous Delivery Phase

When intensive testing has completed, groups can proceed onward to the non-stop conveyance stage. An engineer must physically activate the conveyance of code. However, the remainder of the procedure is completely programmed. All fundamental communication with web workers, databases, and different administrations is finished with the call of content.


CI/CD at the Edge

CI/CD programming pipelines are especially useful while sending in high-chance conditions. At the edge, there is an absence of physical access that can some of the time make it hard to moderate issues. Utilizing consistent incorporation and ceaseless conveyance diminishes the hazard by supporting little, gradual changes to an application. Issues would then be able to be quickly recognized and alleviated before harming creation conditions.

Examples of CI/CD Tools



Jenkins is an open-source automation tool where the focal form and persistent coordination process happens. The program is a Java-based self-containing program with bundles for Windows and MacOS.


Jenkins Key Highlights
  • Open-source
  • Simple establishment and move up to different working frameworks
  • Essential and straightforward to utilize interface
  • Extensible with an immense network-based module asset
  • Simple, straightforward setup
  • Assemble plans dependent on phrases
  • Supports execution of Windows shells and orders in pre-fabricated steps
  • Supports notice of fabricating status



CircleCI is a CI/CD device that bolsters the fast turn of events and the arrival of the product. CircleCI empowers mechanization over the client’s pipeline, from code building to testing and sending.


CircleCI Key Highlights
  • Fits into Bitbucket, GitHub, and Cloud Enterprise
  • Utilizes a compartment or a virtual machine to manufacture
  • Clear investigating
  • Automate parallel build steps
  • Quick Testing
  • The organization is non-stop and branch-explicit
  • Very customizable
  • Automation of combination and custom parcel transfer orders
  • Fast arrangement and boundless development




Bamboo Key Highlights
  • Supports up to 100 remote build agents
  • Run test clumps in resemble and get quick input
  • Integrates with AWS, Docker, and Amazon
  • Makes pictures and pushes to a record
  • Per-environment permissions
  • Distinguishes new branches in Git, Mercurial, SVN Repos and consequently applies the mainline CI plan to them



TeamCity is a Java-based build management and CI server from JetBrain. TeamCity supports building and deploying different types of projects. It can be installed on Windows and Linux servers and supports technologies like .NET. Additionally, the tool can be integrate with other tools, like Docker, Jira, Maven, and Azure, Amazon EC2, and Google Cloud.


TeamCity Key Hightlights
  • Gives a few different ways to the sub-project to reuse parent venture settings and arrangements
  • The equal runs chips away at different conditions all the while
  • Permits to assemble history, see test history reports, pin, tag, and include top choices
  • Simple to modify, collaborate, and worker expansion
  • Keeps the CI Server steady and utilitarian
  • Adaptable client the board, the task of client jobs, the gathering of clients

LoadView: Real Browser-based Load and Stress Testing from the Cloud

The LoadView platform is a flexible load and stress testing platform that addresses the issue of ineffective load patterns, simulating everything from protocol-based tests to real browser-based tests.

Performance testing usually requires additional infrastructure and resources that some organizations may not be able to support. LoadView manages this for you through the platform. The platform is completely cloud-based, so there’s no need to setup or deploy any internal load injectors, manage third-party cloud accounts, or worry about hardware or software requirements.


LoadView Features

load stress performance testing

  • Protocol-level and real browser-based testing
  • Advanced scripting in 40+ desktop/mobile browsers and devices
  • Load curve options – load step, goal-based, and dynamic adjustable curves
  • Test from nearly 30 global locations
  • Scale from dozens to thousands of virtual users
  • Measure response time as perceived by users
  • Reuse load testing scripts for monitoring in production

These features put the process of performance testing into users’ hands, setting LoadView apart from other load testing solutions on the market today, like Gatling or JMeter. Open-source tools like Gatling and JMeter just don’t have the same features and functionalities compared to the LoadView platform.  Read more about all the features of LoadView.


Jenkins: Building, Testing, & Deploying Code


We touched on Jenkins earlier in this article, but just to reiterate, Jenkins is an open-source automation platform, written in Java, with modules designed for continuous integration purposes. Jenkins is designed for building and testing your product development, always making it more straightforward for engineers to incorporate changes to the project.  Likewise, it permits you to ceaselessly convey your product by coordinating with countless testing and organizational innovations.

With Jenkins, associations can quicken the product advancement process through an automation console. Jenkins coordinates improvement life cycle procedures of different types, including manufacture, report, test, bundle, stage, send, static examination, and considerably more.  Modules permit the mix of various DevOps stages. If you need to coordinate a specific device, you have to introduce the modules for that instrument.


When Jenkins is Used

The Jenkins console can be used in many different ways, but it is very supportive in Agile because Dev and QA are working side by side. For example, whenever a developer pushes a new code on a version control system, such asGit, Bitbucket, etc., then a job will be triggered to deploy the build within the QA environment.  After the successful deployment, automated test suites will trigger and the resulting reports will be sent by Jenkins.  Jenkins is very flexible and provides many plugins to help support third-party integrations, and it is also very simple to setup/configure.


Why Jenkins is Used

Continuous integration and continuous deployment concepts have become the backbone of the latest DevOps environment.  It not only bridges the gap in the middle of development and operations teams by automating build, test, and deployment of applications, but they have also has made the process much more efficient. In a trend of continuous development, continuous testing, continuous integration, continuous deployment, and continuous monitoring, all processes of project development, a tool like Jenkins is a complete package that fulfills all challenges. It not only makes development life cycles shorter, but also results in greater customer satisfaction that every company wants.


Jenkins Pipeline

Another major part of Jenkins tool is the Jenkins Pipeline. The Jenkins Pipeline displays an overview about the different jobs running on builds after commits made by developers. It notifies about the tasks Jenkins is currently executing.  In the build pipeline, the build can be seen as divided into sections, such as the unit tests, acceptance tests, and packaging, reporting, and deployment, phases. These phases can be performed either in a series, or parallel. If one phase is successful, it automatically proceeds on to the next phase, thus referring to its name ‘Pipeline.’

As several various changes are being committed by different developers at once, it is helpful to know which change is getting tested now, or which change is sitting in line, perhaps due to a failed build. Once the build has passed unit and integration testing, then engineers in test automation services use Jenkins to trigger automation suites and email reports once the job is ended.

The Jenkins console gives us various interfaces and tools to work with in order to automate the whole process. Jenkins is used to build and test your software projects continually making it easier for developers to integrate changes to the project, and making it effortless for users to obtain a fresh build. It also authorizes you to continuously deliver your software by integrating with a large number of testing and deployment technologies.

LoadView Plugin for Jenkins Requirements


Utilizing the LoadView Plugin for Jenkins, performance testing teams can easily incorporate real browser-based load testing into their Jenkins test builds. This ensures that applications are continuously being tested and evaluated over longer periods of time. This allows teams to identity and address errors and bottlenecks before code and applications are pushed into production.

The primary objective of load testing is rather obvious, to define how much workload the system can take before breaking down or stalling, but the process can be much more complex that just that.  A solution like LoadView simplifies what used to be a time consuming process.  Exposing a system to large amount of load, or virtual users, allows you to reveal weak points of the system with detailed specifics regarding the source of the problem before additional damage is done.  Aside from helping to locate issues, load testing also provides performance results through waterfall charts, test results, and benchmarks from comparative tests. It makes it clear when and why the problem occurred and what caused it to happen.


*Before using the LoadView Plugin for Jenkins, you must first have an active Jenkins and LoadView account and configure a stress test scenario.

Try LoadView Free!

No credit card, no contract.

Create a Unique Identifier for Jenkins Integration


To set up an integration with Jenkins, you will first need to create a Unique Identifier (UID) to use as a LoadView Security Token. To create your UID, follow these simple steps:

LoadView Plugin for Jenkins Integration UID


1. Log into your LoadView account

2. From the Account menu, select Integrations

3. Select Add Integration

4. Select Stress Testing Web API. A UID will automatically be created.

5. Copy the integration UID to use in Jenkins.




As a general note about Integration types, you can create as many Integration types as needed. Each integration has a Unique Identifier (UID) that will be required during setup.  To create an Integration and UID, select the Add Integration button above and select the Integration Type. A secure UID will be created automatically.

LoadView Plugin Installation in Jenkins


1.  Log into your Jenkins account

  • Select Add Credentials from the Credentials menu
  • Select the LoadView Security Token (UID).



LoadView Plugin for Jenkins Add Credentials2.  Configure and validate the credentials

  • Kind.  LoadView Security Token (UID).
  • Scope. Select Global.
  • ID. Leave default or specify a unique ID.
  • Description. Specify a unique description to distinguish the credentials.
  • UID. Paste the LoadView UID from your LoadView account. Once the UID has been added, click Validate UID to make sure Jenkins can access the LoadView API.



3.  Select a job and click Configure

  • Go to Build > Post-build Actions > Add Post-build Action > LoadView-Run load test scenario
  • Specify LoadView Stress Test settings for your Jenkins Build

LoadView Plugin for Jenkins Post-build Actions

  • Credentials. Select the API key using the description.
  • Scenario ID. Paste the stress test scenario ID you want to use in the build. Copy the ID from the scenario page in LoadView.
  • Error Threshold. Specify an acceptable percentage of sessions with errors that occur during the test (for example, failed to access the target resource, no keywords/image found, etc.). If the percentage of error sessions is greater than the specified value, the build will be marked as a failure in Jenkins.
  • Average Time. Specify a limit for an average response time measured during test execution. If the limit is reached, the build will be marked as a failure in Jenkins.

4.  Save your Build Actions

LoadView Test Results


When a test is running, the status of execution is displayed in the Jenkins Console Output in real-time mode.

LoadView plugin for Jenkins

Once the test has been finished, the results can be found under LoadView Results in the Jenkins Build menu.

  • Test duration
  • Maximum number of virtual users
  • Total sessions
  • Successful sessions
  • Failed sessions
  • Uncompleted sessions



Select More Details to review more comprehensive LoadView performance reports.

Flexible. Scalable. Powerful.

All from one convenient load testing platform.