Merge pull request #81 from veracode/SDEVX-8215

Changes for SCA Scan to support break build on policy findings.

Author: veraakarthikbharadwaj

.github/workflows/binary-ready-veracode-sast-policy-scan.yml

@@ -88,6 +88,7 @@ jobs:
           failbuild: ${{ github.event.client_payload.user_config.break_build_policy_findings }}
           deleteincompletescan: true
 
+
       - name: Veracode Policy Results
         id: prepare-results
         if: always()

.github/workflows/veracode-sca-scan.yml

@@ -82,9 +82,10 @@ jobs:
         env:
           SRCCLR_API_TOKEN: ${{ secrets.VERACODE_AGENT_TOKEN }}
           JAVA_OPTS: -Xms2g -Xmx4g
-        uses: veracode/[email protected].13
+        uses: veracode/[email protected].14
         with:
           github_token: ${{ secrets.GITHUB_TOKEN }}
           create-issues: false
           recursive: true
           allow-dirty: true
+          breakBuildOnPolicyFindings: ${{ github.event.client_payload.user_config.break_build_policy_findings }}

veracode.yml

@@ -57,6 +57,7 @@ veracode_sca_scan:
   # If the break_build_on_error is set to true, the build will break if the scan failed to complete or with an error, no libraries were found, 
   # or no build system was found and the error_message will be displayed.
   break_build_on_error: true
+  break_build_policy_findings: true
   error_message: "Veracode SCA scan faced a problem. Please contact your Veracode administrator for more information."
   # If the trigger is set to true, a scan is triggered when you create an issue containing the commands value or add a comment containing the commands value to an issue.
   # Syntax to be used - COMMANDS_VALUE [branch: BRANCH_NAME]