
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Does anyone know the command to extract the Build Label
from FPR file using the FPRUtility tool?
I tried the below command but does not give the Build Label
.
sca18.20/bin/FPRUtility -information -search -project prevresults.fpr -query "[Build Label]" -f output.txt
Attached snapshot from SSC which shows the field [Build Label]
in which I am interested to extract using FPRUtility. This is required for one automation task.
Please note: I am using Fortify 18.20.
Accepted Solutions

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
There is not a way to extract the Build Label for the FPR file using the FPRUtility. The -search parameter Searches the fpr for issues based on the query parameter. So basically your command is looking of issues that are related to "[Build Label]" . You would have to extract the audit.fvdl file manully for the FPR and pares the file to get the label. You could get this info using the SSC API but you will have to know the artifact ID. How are you passing the -build-label switch in SCA?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
There is not a way to extract the Build Label for the FPR file using the FPRUtility. The -search parameter Searches the fpr for issues based on the query parameter. So basically your command is looking of issues that are related to "[Build Label]" . You would have to extract the audit.fvdl file manully for the FPR and pares the file to get the label. You could get this info using the SSC API but you will have to know the artifact ID. How are you passing the -build-label switch in SCA?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Thanks for your suggestion. I did extract the audit.fvdl from FPR and got the Build Label. Before posting the query in this forum, we had tried the SSC Api route but that was tedious and over complicated for a simple automation task as it involved multiple steps and also required us to create a new read only user to access the SSC API:
- Get the application version using fortifyclient utility
- Get the artifacts using SSC Api
- Extract the href from first node of JSON returned in step 2
- Travel to the href url extracted in step 3
- Extract one more href from the JSON returned in step 4
- Travel to the href url extracted in step 5
- Finally you get the buildLabel in JSON returned in step 6
We are passing the build label via sourceanalyzer command during translation step. Again, many thanks for your suggestion.