...
| Info | ||
|---|---|---|
| ||
As said in the description above, this plugin imports audit reports available in Fortify SSC Server. This means that the plugin:
As a consequence, Fortify scans must have been run before executing this plugin on Sonar. The plugin has been developed and tested with Fortify 2.50. Older versions might also work (feel free to tell us on the user mailing list if you managed to make it work in this case). |
| Note | ||
|---|---|---|
| ||
The Fortify plugin currently does not support multi-module for languages other than Java. You can watch and vote for the following JIRA ticket concerning this issue: SONARPLUGINS-2452 |
Here are some screenshots of the plugin:
...
- Configure the connection to the Fortify SSC Server in Configuration Settings > Configuration > General Settings > Fortify:
- Server URL
- Login/password. Token-based authentication is not supported yet.
- Activate some Fortify rules in the Quality Profile
- Configure the project to be analyzed:
- By default project name and version must match the name and version defined in Fortify. They can be changed in Project Settings.
- Enable audit import on the projects that have been scanned by Fortify: set
sonar.fortify.enabletotruein Project Settings.
Inspect project. The following logs should appear:
Code Block [INFO] [14:03:32.720] Fortify SSC Project: <Fortify project name>, version: <Fortify project version> [INFO] [14:03:35.643] Sensor Fortify Audit Context... [INFO] [14:03:35.643] Sensor Fortify Audit Context done: 0 ms [INFO] [14:03:35.643] Sensor Fortify Performance Indicators... [INFO] [14:03:36.701] Sensor Fortify Performance Indicators done: 1058 ms [INFO] [14:03:36.701] Sensor Fortify Issues... [INFO] [14:04:35.131] Loading 171 Fortify issues [INFO] [14:04:35.149] Sensor Fortify Issues done: 58448 ms
...
