How do I use Polyspace Bug Finder with Jenkins?

75 views (last 30 days)
I would like to use Polyspace Bug Finder in a continuous integration system mechanism.

Accepted Answer

MathWorks Support Team
MathWorks Support Team on 15 Jun 2021
Edited: MathWorks Support Team on 16 Nov 2021 at 11:50
R2018b and earlierIn the zip package attached to this article you will find information to create a Polyspace Bug Finder demo with Jenkins in a very easy way. The workflow of the demo is the following:
  • polyspace-configure monitors the compilation of your complete project (a build “all”) and creates a project file (an options file).
  • Then Polyspace Bug Finder analysis starts on the built files.
  • Polyspace import comments, at end of the analysis, executes a difference between previous job results and current job results.
  • One Perl script parses the two last log files and the difference between the two last runs to check defects and coding rules.
  • At last, an E-mail will be sent with the difference.
  • From E-mail sent, you can open last results, and you see defects and coding rule violations
Even if It is not the real workflow that you want to apply, I guess it will provide some ideas how to implement it. The Docs sub-folder in zip file contains a QRG.R2019a onwards
The 'MathWorks Polyspace plugin' in Jenkins allows you to run the Polyspace Server products as part of continuous integration.
After you install the Polyspace Server (and Polyspace Access) products, you can download the plugin from Jenkins and point the plugin to your product installation. The plugin provides these features:
  • Running Polyspace Bug Finder Server or Polyspace Code Prover Server on checked-in C/C++ code
  • Uploading Polyspace results (bugs, run-time errors, coding standard violations, code complexity metrics and other findings) to the Polyspace Access web interface for review
  • Setting up pass/fail criteria for builds based on Polyspace results
  • Filtering results based on predefined criteria such as file ownership or impact of defects
  • Sending e-mail notifications with new findings to file owners
For an overview of the plugin, see MathWorks Polyspace plugin .
For a quick start and example scripts, see MathWorks Polyspace plugin repository in Github .
For a more detailed tutorial, see the Polyspace documentation .

More Answers (1)

Anirban
Anirban on 27 Mar 2019
In R2019a, the 'MathWorks Polyspace plugin' in Jenkins allows you to run the Polyspace Server products as part of continuous integration.
After you install the Polyspace Server (and Polyspace Access) products, you can download the plugin from Jenkins and point the plugin to your product installation. The plugin provides these features:
  • Running Polyspace Bug Finder Server or Polyspace Code Prover Server on checked-in C/C++ code
  • Uploading Polyspace results (bugs, run-time errors, coding standard violations, code complexity metrics and other findings) to the Polyspace Access web interface for review
  • Setting up pass/fail criteria for builds based on Polyspace results
  • Filtering results based on predefined criteria such as file ownership or impact of defects
  • Sending e-mail notifications with new findings to file owners
For an overview of the plugin, see MathWorks Polyspace plugin.
For a quick start and example scripts, see MathWorks Polyspace plugin repository in Github.
For a more detailed tutorial, see the Polyspace documentation.
  3 Comments

Sign in to comment.

Tags

No tags entered yet.

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!