In this section:
The Parasoft Findings Plugin for Jenkins allows you to visualize static analysis and test results in Jenkins. It converts XML reports generated by Parasoft products into trend graphs and enables you to conveniently view the details or easily navigate to rule documentation. The plugin can be used with Freestyle, Maven, and Pipeline jobs.
The plugin can consume the following report types:
The simplest installation method is to use the Jenkins plugin UI:
Alternatively, you can download the plugin from Parasoft's GitHub repository and follow the instructions to build the plugin as an HPI file (plugin format for Jenkins): https://github.com/jenkinsci/parasoft-findings-plugin. After creating the HPI file, you can deploy the plugin through the Jenkins web UI or through the command line.
See the Jenkins documentation for command line installation. Restart Jenkins after installing the plugin.
You can use the plugin with new and existing Jenkins jobs.
report.locationproperty, which specifies where the report.xml file is saved. See the documentation for your analyzer for additional information about configuring the settings file.
You can also enable the Report location option and specify a workspace-relative path to the report.xml file generated by Parasoft Analyzer in the File pattern field. This setting overrides the
report.location configuration from the previous step and is useful when Jenkins and the directory for the report.xml file are both on the local machine.
C++test 10.x Desktop reports for static analysis must be generated with the Add absolute file paths to XML data option enabled. You can enable this option on the command line by setting the
report.rulesproperty to the directory that contains the analyzer documentation. For example:
Specify a workspace-relative path to the report.xml file generated by Parasoft Analyzer in the Pattern field.
C++test 10.x Desktop reports for unit test results must be generated with the Overview of checked files and executed tests option enabled. You can enable this option on the command line by setting the
Jenkins Pipeline is a suite of plugins that support implementing and integrating continuous delivery pipelines into Jenkins. See the Jenkins documentation for additional information about pipelines.
To publish static analysis results using a pipeline job, add a step to the pipeline script to call the Parasoft Findings publisher class or use the symbolic name:
step([$class: 'ParasoftPublisher', useReportPattern: true, reportPattern: '*.xml', settings: ''])
parasoftFindings useReportPattern: true, reportPattern: '*.xml', settings: ''
The parameters passed correspond to the options following available in plugin configuration:
|useReportPattern||Report location option|
|reportPattern||File pattern field|
To publish unit and functional test results using a pipeline job, add a step to call the xUnit publisher class and specify the appropriate type of reports to publish:
step([$class: 'XUnitBuilder', tools: [[$class: 'ParasoftType', pattern: '']]])
step([$class: 'XUnitBuilder', tools: [[$class: 'ParasoftSOAtest9xType', pattern: '']]])
Static analysis trend graphs display results organized by the module, rule category or severity.
You can review the findings in the source code and navigate to rule documentation.
The test execution trend graphs shows test status, execution time, and stack trace for test failures.
Fixed an issue related to resolving environment variables when static analysis results are imported.
Added support for static analysis and unit test results for C++test 10.x Desktop.
Added support for pipelines.
Fixed wrong number of test results reported in some cases.
Fixed handling error messages and stack traces for tests having multiple failures.
Fixed missing "time" attributes not handled properly.
Fixed not using correct "time" attribute in some cases.
|10.3.3||Updated Parasoft Services to 10.3.3.|
Fixed the issue with Parasoft Findings Plugin not working with analysis-core version 1.82.
Updated Parasoft Services to 10.3.2.
Added publishing functional test results from Parasoft SOAtest 9.x reports.
Updated Parasoft Services to 10.3.0.
Fixed an issue with visualization of parameterized test results.
Updated Parasoft Services to 10.2.3.
|10.2.2||Initial release based on Parasoft Services 10.2.2.|