JPanni198706 (Community Member) asked a question.
Is there a way to stop the Veracode Flaw Importer from progressively taking longer and longer to complete?
The Veracode Flaw Importer appears to query every past build, as each new scan is completed, 4 to 5 seconds is added to our pipeline duration.
Every couple of weeks we add another minute to our pipeline. It is getting to the point where this is no longer sustainable.
.png){kind=logo}
Hello @JPanni198706 (Community Member) ,
If you feel that your scans are getting slower and slower I would break up the code because sometimes the file size can be a factor in the amount of time it takes to complete the scan.
Please ensure that you are following the Veracode general packaging guidelines and you can schedule a consultation call to go over your code/upload.
Jason
Veracode Support Engineer
Hi Jason,
The question relates to the Azure DevOps Flaw Importer (https://docs.veracode.com/r/t_importflaws) not the scan itself.
Apologies if this wasn't clear.
Hi @JPanni198706 (Community Member) thank you for bringing this request to our attention, I will look further into this to identfy possible solutions.
Thanks Mike.
We are having the same issue. We have a profile with over 1100 static scans. We can't even delete them as it was advised we do. It says we can only delete the latest one.