PLakhani132493 (Community Member) asked a question.
What is basic difference if I use jenkins veracode plugin vs pipelinescan.jar ?
Hi Team,
We are having some confusion related what are basic difference between if we use the jenkins veracode plugin vs library pipeline scan jar ?
- Is pipleine scan(jar) is faster then jenkins plugin, is it do local scan on my jenkin node ???
- is pipeline scan result will reflect into the sandbox or application ?
- with piplelinescan jar , can I have dashboard like varacode scan result which shown after the scanning with plugin with wait as True?
- with piplinescan, Can I get result pdf ?
Regards, Pranav
.png){kind=logo}
Hello @PLakhani132493 (Community Member) ,
Thank you for reaching out to the Community.
Pipeline scanning is meant for CI/CD process. It does not communicate with the Veracode Platform in storing results in any way. The intent for the pipeline scanner in the SDLC is to shift left. So the Jenkins plugin is meant to do Governance and Reporting. So we recommend it be part of a scheduled automated sequence. The pipeline scanner should be utilized with pull requests.
The pipeline scan and its use in Jenkins are also shown in the Veracode Documentation, https://docs.veracode.com/r/Jenkins_Pipeline_Scan_Examples, to elaborate on its recommended CI/CD intended use. This includes that there would not be sandbox or policy results or a specific PDF results file.
Kind regards,
Steven
Veracode Support Engineer
Hi @Steven D., Veracode Support (Veracode) ,
One more question on that, if it is not communicate with veracode platform then while doing pipeline scan it show.
"sending bytes xxxxx" and "upload complete" , will it upload something on veracode? and it is being timeout 60 minute any workaround for it jar file is around 174MB, if we do compress what type of compression is allowed ?
[06 Jul 2022 12:52:04,0682] PIPELINE-SCAN INFO: Beginning scanning of 'service/aaaaaa-onboarding/target/aaaaa-onboarding-1.0.0-SNAPSHOT.jar'.
[06 Jul 2022 12:52:04,0682] PIPELINE-SCAN INFO: Sending 184569371 bytes to the server for analysis.
[06 Jul 2022 12:53:53,0265] PIPELINE-SCAN INFO: Upload complete.
[06 Jul 2022 12:53:53,0265] PIPELINE-SCAN INFO: Scan ID: e514c79b-831e-487b-976b-2a64756dca03
[06 Jul 2022 12:54:08,0408] PIPELINE-SCAN INFO: Analysis Started.
[06 Jul 2022 13:52:04,0682] PIPELINE-SCAN ERROR: User Timeout of 60 minutes hit. Exiting.
Can you please assist us.