We have multiple application running in Veracode platform and generate the static report each application now I want to notify the static scan pdf report to the developer with attachement.we don't want to login developer into Veracode.

1.Do we have any api calls for sending pdf report from Jenkins or Veracode platform ?

2. if Any very high or highs in the static scan report should prevent a promote to next environment from Jenkins.

Hi @jcontti203285 (Community Member)​, thank you for your patience, in response to your questions,

1. Do we have any api calls for sending pdf report from Jenkins or Veracode platform ? --> Unfortunately, we don't currently support this feature. However, as a Veracode customer, you have access to the Ideas forum in the Community where you can make suggestions to our Product team. I'd encourage you to add this Idea if that's something critical to your program.
2. If any very high or highs in the static scan report should prevent a promote to next environment from Jenkins.

https://help.veracode.com/reader/Xsx4w5mUPDcfuttA34wSpw/C92fIf8huqekw081gEoz3A

Applying Rules to a Policy

When creating a policy, you can add several rules that applications must follow to pass the policy.

Findings by Severity

Select one or more scan type options and select a severity requirement. Applications must not contain any findings of the selected severity or higher in scans of the selected scan types.

After setting the criteria to possibly fail a scan's policy due to the severity of the flaws, you can check the checkbox to fail the scan,

Share URL

Configuring Jenkins to Use the Veracode Jenkins Plugin

https://help.veracode.com/r/c_jenkins_config_plugin

* Select the Fail Job checkbox to stop the build from completing in specific circumstances. If the process of uploading to Veracode does not succeed or if the Veracode scan fails, you have the option of stopping the build to prevent further processing time being spent on the build. Several conditions could cause a scan to fail, including network timeouts, incorrect credentials, or exceeding the maximum file size when uploading. The Fail Job option allows you to stop a build if either of these specific failures occurs:

• During an upload and scan, an SCA scan or static scan fails a specified policy evaluation.
• A dynamic rescan post-build action fails.

The Fail Job selection is optional. However, this option can save you time and enable you to quickly troubleshoot build issues that are related to your Veracode scan.

15. Select the Wait for scan to complete checkbox if you want the Jenkins job to wait for the Veracode scan to complete.Enter the maximum time in minutes that you want the Jenkins job to wait before skipping the Upload and Scan with Veracode action. Allow enough time for a typical scan of your application to complete. A Veracode policy scan fails, regardless of whether it completes or not, if it does not meet the requirements of the associated policy.