Fortify 360 FPR post-processing and uploading to Fortify 360 Server
The easiest way to setup is to include Fortify into your PATH environment.If you don't want to add Fortify into your PATH, then setup as follows:
You don't need to install Fortify on the master node, you just need to copy the following 4 jars from a Fortify installation and setup the path in global config
Since we need to run "reportGenerator", you need to install Fortify on the slave node. If we can't find "reportGenerator" we will skip plotting the NVS chart, other features are not affected.
We will try to locate "reportGenerator" in the following order:
- The plugin uses "reportGenerator", which is installed with Fortify 360, to generate XML report to retrieve FPR summary data.
- Starting from v2.0, it will use WS call to upload FPR to Fortify 360 Server directly. Before v2.0, it uses "fortifyclient" to upload FPR to Fortify 360 Server.
We assume the FPRs are stored inside the workspace (which can be a remote slave machine), not the Build RootDir (which is in the master machine).
samngms [at] gmail [dot] com
Version 3.90 (Jun 28, 2013)
Version 3.81 (April 8, 2013)
Version 3.6 (Nov 28, 2012)
Version 2.4 (May 26, 2012)
Version 2.3 (Dec 24, 2011)
Version 2.2 (June 13, 2011)
Version 2.1 (Oct 11, 2010)
Version 2.0 (Sep 3, 2010)
Version 1.4 (May 24, 2010)
Version 1.3 (April 6, 2010)
Version 1.2 (April 5, 2010)
Skip to end of metadata Go to start of metadata