Plugins

This section provides information on the LoadRunner Enterprise plugins for continuous integration (CI).

In this topic:

About LoadRunner Enterprise CI plugins

The LoadRunner Enterprise plugins for continuous integration provide a mechanism for executing performance tests as part of a build script.

These plugins allow you to trigger a LoadRunner Enterprise test as a build step and present the results in the CI server's user interface.

For LoadRunner Enterprise's CI plugin tools to integrate securely with LoadRunner Enterprise, you must configure the following:

SSO or LDAP authentication must be enabled on the LoadRunner Enterprise server. For details, see SSO authentication and LDAP authentication.
LoadRunner Enterprise must have an API access key which it uses during authentication. The LoadRunner Enterprise site administrator configures a unique pair of ClientId and ClientSecret keys for a specific user, which enables that user to login using a REST API. For details, see Set up API access.

Plugins are available for various CI servers. Visit the plugin page for your CI server for more details:

Plugin	Description
Jenkins	Enables you to run LoadRunner Enterprise tests as part of your Jenkins continuous integration process.
Git	Enables you to synchronize LoadRunner Enterprise with Git by uploading performance test scripts stored in a GitHub repository to a LoadRunner Enterprise project. You can also synchronize tests from YAML files saved in a GitHub repository, and create tests from YAML input and run the tests.
Bamboo	Enables you to run LoadRunner Enterprise tests as part of your Bamboo continuous integration process to ensure that new builds have not introduced any regressions.
TeamCity	Enables you to run LoadRunner Enterprise tests as part of your TeamCity CI/CD process.
Azure DevOps (previously TFS/VSTS)	Enables you to run LoadRunner Enterprise tests with the Azure DevOps CI system, previously named Visual Studio Team Foundation Server (VSTS or TFS).