Performance Center and Git

This topic describes how to integrate Performance Center with Git via Jenkins, using the Performance Center-Git integration plugin.

Note: There is another plugin for running performance tests using Performance Center. For details, see Performance Center and Jenkins.

About the Performance Center-Git integration

This integration enables you to:

Synchronize scripts

Synchronize scripts by uploading LoadRunner and JMeter scripts stored in a GitHub repository to a Performance Center project. For details, see Synchronize Performance Center with Git.

Available in plugin versions: 1.0.0 and later

 
Synchronize tests

Synchronize tests from YAML files saved in a GitHub repository to a Performance Center project. For details, see Synchronize Performance Center with Git.

Available in plugin versions: 1.1.0 and later

 
Run tests

Create tests from YAML input added to a field within the Jenkins Job configuration, and then run the tests. For details, see Run a performance test using Performance Center.

Available in plugin versions: 1.1.0 and later with Performance Center 12.61 and later

 

Back to top

Tips and troubleshooting

This section provides information for troubleshooting issues related to the Performance Center integration with Git.

Supported/ compatible versions

The PC-Git plugin is supported in Performance Center versions 12.60 and later, and is compatible with Performance Center versions 12.55-12.57 with the following limitations:

  • In Performance Center, you need to manually create the Test Plan folder specified in the Test Plan folder field of the step build (see step 2e in Configure a job in Jenkins to synchronize scripts) before running any build.

  • All scripts found in the Git repository will be uploaded to the same root folder in Performance Center 12.55-12.57. As a result, any scripts with the same name will overwrite each when uploaded to the Performance Center project.

Uploading builds

The first successful build uploads all scripts (this might take longer to sync). Subsequent builds include modifications from the previous successful build only, and should be much faster.

Deleting scripts

Synchronizing script deletion is optional in the build's configuration (it is enabled by default). However, failing to delete scripts in a Performance Center project after they have been deleted in the Git repository will not cause the build to fail.

Version control Performance Center projects with Version Control enabled are not supported.

Back to top