The Pipeine Scan --include parameter and the scanned file size
If the Pipeline Scan execution returns an error like, "PIPELINE-SCAN ERROR: CREATE FAILURE: HTTP Response 400: The upload binary 315052540 is too large. Max upload limit is 209715200 bytes", the --include parameter that filters the scanned modules will NOT solve this problem.
Reducing the artifact file size or 'chunking' it to separated scanned files can be the solution.
However, with the changes Veracode is making over the course of time, we should be able to relax or remove those upload size limits in future, at which point --include would help with the scan performance.
At present, you can use the --include parameter to select the modules which you would want to be scanned from the list of scannable modules identified as part of the pipeline scan.
Related Articles
Not able to Promote a Sandbox Scan to the Policy Scan Number of Views How to download only Dynamic scan result report only. Number of Views What is the meaning of Partial Results Available for the scan? Number of Views What does "The following modules were not selected for a full scan" mean in the PDF report for the scan? Number of Views Why is no source code info displayed for certain scans under Triage Flaw? Number of Views
This topic isn't available in this community.
Related Topics
Ask the Community
Get answers, share a use case, discuss your favorite features, or get input from the Community.
.png){kind=logo}
