Plug-ins

This section provides information on the plug-ins for continuous integration (CI).

About CI plug-ins

The plug-ins for continuous integration provide a mechanism for running performance tests as part of a build script.

These plug-ins allow you to trigger a performance test as a build step and present the results in the CI server's user interface.

Configure the following for CI plug-in tools to integrate securely with OpenText Enterprise Performance Engineering:

SSO or LDAP authentication must be enabled on the OpenText Enterprise Performance Engineering server. For details, see SSO authentication and LDAP authentication.
OpenText Enterprise Performance Engineering must have an API access key which it uses during authentication. The 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.

Plug-ins are available for CI servers. Visit the plug-in page for your CI server for more details.

Plug-in	Description
Jenkins	Enables you to run performance tests as part of your Jenkins continuous integration process. For details, see Jenkins plug-in.
GitHub	Enables you to design and run performance tests as part of your GitHub continuous integration process. For details, seeGitHub action.
GitLab	Enables you to design and run performance tests as part of your GitLab continuous integration process. For details, see GitLab integration.
Bamboo	Enables you to run performance tests as part of your Bamboo continuous integration process to ensure that new builds have not introduced any regressions. For details, see Bamboo plug-in.
TeamCity	Enables you to run performance tests as part of your TeamCity CI/CD process. For details, see TeamCity plug-in.
Azure DevOps	Enables you to run performance tests with the Azure DevOps CI system, previously named Visual Studio Team Foundation Server (VSTS or TFS). For details, see Azure DevOps plug-in.