mmkaminski (Community Member) asked a question.
Hi, I'm trying to shift our Veracode scanning over to the pipeline scan tool from the Jenkins plugin (the speed of that is far too slow for pipeline scans) but it seems the artifact size limit is a bit too restrictive:
```
09:40:57 [03 Jun 2020 09:40:57,0616] PIPELINE-SCAN INFO: Pipeline Scan CI Tool Version 20.5.6-0.
09:40:57 [03 Jun 2020 09:40:57,0619] PIPELINE-SCAN INFO: Beginning scanning of 'build/libs/batch-0.20200603.0940.b953998-US338678.jar'.
09:40:57 [03 Jun 2020 09:40:57,0620] PIPELINE-SCAN INFO: Sending 128900653 bytes to the server for analysis.
09:40:59 [03 Jun 2020 09:40:59,0318] PIPELINE-SCAN ERROR: PREFLIGHT FAILURE: HTTP Response was 413: The upload is too large. Max upload: 104857600 bytes
09:40:59 [03 Jun 2020 09:40:59,0318] PIPELINE-SCAN ERROR: The scan failed to complete: there are no results to analyze.
```
We're building Sprint Boot jars and they typically come in at around 125MB up to maybe 200MB. A 104-ish MB upload size limit is simply not sufficient for our use, and I can't imagine that we're particularly special in that. Is there any plan on increasing that upload limit? 200MB would suit us, I'm sure others have larger artifacts that they need to scan.
.png){kind=logo}
That's supposed to be MAX Upload Size Problem, yay fingers!
I have the same problem.
PIPELINE-SCAN ERROR: PREFLIGHT FAILURE: HTTP Response was 413: The upload is too large. Max upload: 104857600 bytes
My WAR file is 146 MB. I could remove some of the dependencies to trim it down, but I want those scanned for vulnerabilities too. Manual upload limit is 2 GB. I don't understand why the pipeline upload is so limited.
We reported this too and awaiting resolution.