Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

You can For details on how to run Performance Center tests using Jenkins continuous integration. For details, see the Performance Center Help Center.

Table of Contents

Set up a job

...

and

...

  • Automatically select existing or create new if none exists (Performance Center 12.55 or later). If you select this option, Performance Center creates a test instance or locates the existing test instance.
  • Manual selection. Enter the Test Instance ID (available from My Performance Center > Test Management > Test Lab > Performance Test Set view).

...

  • Do Not Trend. No trend report is created.
  • Use trend report associated with the test (Performance Center 12.55 or later). If Auto Trending is selected in the Load Test, select this option to automatically publish trend results.
  • Add run to trend report with ID. If you select this option, enter the trend report ID (supported for version 12.53 or later).

...

Set up the Post Build actions

  1. In the Post-build Actions section, expand the Add post-build action drop-down and select Publish test result.
  2. Select a report archive mode.

Run the job

Run or schedule the job as you would with any standard Jenkins job.

Review the results

  1. From the dashboard, click on the job.
  2. Click the Console link to view the PC run information.
  3. When the Collate and Analyze option is set as the post run action, the Performance Center HTML report can be viewed and downloaded directly from Jenkins via the Build Artifacts or Test Result options.
    Image Removed

Configure Trending Report Charts on Jenkins

...

  • Plot group. Enter a meaningful name for the group. For example, Performance Trending.
  • Plot title. Enter a name that is related to the measurement. For example, Average Transaction Response Time.
  • Number of builds to include. Enter the number of builds to include. We recommend no more than 10 builds.
  • Plot y-axis label. Enter the appropriate measurement unit. For example, Seconds. See the recommended unit for each measurement in the table below.
  • Plot style. Select the plot style. Line or Line 3D are the most suitable for trending.
  • Data series file. Enter one of the measurement types listed in the table below.
    (Tip: We recommend using the bolded measurements for trending because they compare like-for-like measurements to provide an indication of the application’s performance and workload.)
  • Load data from csv file. Select this check box.
  • Make sure Include all columns is selected.
  • Display original csv above plot. Select this check box.

...

Data Series Files

...

Type

...

Data Series File

...

Comment

...

Unit

...

TRT (Transaction Response Time)

...

pct_minimum_trt.csv

...

Minimum transaction response time

...

Seconds

...

pct_maximum_trt.csv

...

Maximum transaction response time

...

Seconds

...

pct_average_trt.csv

...

Average transaction response time

...

Seconds

...

pct_median_trt.csv

...

Median transaction response time

...

Seconds

...

pct_percentile_90_trt.csv

...

90th percentile of transaction response time

...

Seconds

...

pct_stddeviation_trt.csv

...

Standard deviation transaction response time

...

Seconds

...

pct_count1_trt.csv

...

Number of occurrences of the transaction

...

Count

...

TPS (Transaction per seconds)

...

pct_minimum_tps.csv

...

Minimum transaction per second

...

Count

...

pct_maximum_tps.csv

...

Maximum transactions per second

...

Count

...

pct_average_tps.csv

...

Average transactions per second

...

Count

...

pct_median_tps.csv

...

Median transactions per second

...

Count

...

pct_sum1_tps.csv

...

Total amount of transaction per second for a given transaction

...

Count

...

TRS (Transaction Summary)

...

pct_count1_trs.csv

...

Total amount of occurrences for a given transaction

...

Count

...

UDP (User defined data point)

...

pct_minimum_udp.csv

...

Minimum value for a user defined data point

...

Unit

...

pct_maximum_udp.csv

...

Maximum value for a user defined data point

...

Unit

...

pct_average_udp.csv

...

Average value for a user defined data point

...

Unit

...

pct_median_udp.csv

...

Median value for a user defined data point

...

Unit

...

pct_stddeviation_udp.csv

...

Standard deviation value for user defined data point

...

Unit

...

pct_count1_udp.csv

...

Number of occurrences for a given user defined data point

...

Count

...

pct_sum1_udp.csv

...

Sum of the values reported in a given user defined data point

...

Unit

...

VU (Running Vusers)

...

pct_maximum_vu.csv

...

Maximum number of running Vusers in the scenario

...

Count

...

pct_average_vu.csv

...

Average number of running Vusers in the scenario

...

Count

...

WEB

...

pct_minimum_web.csv

...

Minimum value of web statistics (# of connections, throughput, hits per second, etc.)

...

Unit

...

pct_maximum_web.csv

...

Maximum value of web statistics

...

Unit

...

pct_average_web.csv

...

Average value of web statistics

...

Unit

...

pct_median_web.csv

...

Median value of web statistics

...

Unit

...

pct_sum1_web.csv

...

Total value of web statistics

...

Unit

Note: If you get a file does not exist error (“<file_name.csv> doesn’t match anything”), you can ignore this because the file will be created during the job execution.
Jenkins in the Performance Center Help Center.