Troubleshooting CI/CD system integrations

This section helps you remedy common problems and understand how better to use Veracode CI/CD system integrations.

CI/CD integration	Issue	Solution
Veracode Jenkins Plugin	I receive one of these messages: An app_id could not be located for application profile Access denied Check the Veracode user role for the logged-in account to verify that you have a role with permissions to create an application profile, such as Upload API for API service accounts or Creator for user accounts. Confirm that the Veracode application profile for the specified application name is visible by the specified teams who have access to this application and its scan results.	Check the Veracode user role for the logged-in account to verify that you have a role with permissions to create an application profile, such as Upload API for API service accounts or Creator for user accounts. Confirm that the Veracode application profile for the specified application name is visible by the specified teams who have access to this application and its scan results.
Veracode Jenkins Plugin	This message appears in the console output: The policy status 'Did Not Pass' is not passing. Unable to continue.	This message indicates that you selected the Wait for scan to complete checkbox in your job configuration and the scan failed to pass your policy. If you want builds for scans that fail policy to complete, you must deselect that checkbox.
Veracode Jenkins Plugin	The test connection action fails. There is no success message. - Verify that your Jenkins server has internet connectivity. - Check outside of the Jenkins plugin environment to verify if the server the Jenkins tool is running on has internet connectivity. To determine connectivity, download and run the Java API wrapper on the same machine the Jenkins tools are running on to test for internet connectivity. - Verify the proxy settings to see if a proxy is required. - If a proxy is not required, you can test for an external internet connection with a cURL command and running, for example, the getapplist.do call. - Veracode APIs and integrations require access to analysiscenter.veracode.com and api.veracode.com. Contact your IT team to ensure these domains are on the allowlist for your organization and that there is one-way communication on port 443 to api.veracode.com. Refer to the complete list of domains and IP addresses to add to your allowlist.	- Verify that your Jenkins server has internet connectivity. - Check outside of the Jenkins plugin environment to verify if the server the Jenkins tool is running on has internet connectivity. To determine connectivity, download and run the Java API wrapper on the same machine the Jenkins tools are running on to test for internet connectivity. - Verify the proxy settings to see if a proxy is required. - If a proxy is not required, you can test for an external internet connection with a cURL command and running, for example, the getapplist.do call. - Ensure you have added the required domains for your Veracode account to the allowlist for your organization. Refer to the complete list of domains and IP addresses to add to your allowlist.
Veracode Jenkins Plugin	I see this message: Unknown vid and vkey.	See step 23.
Veracode Jenkins Plugin or Java API wrapper	I see this message: Requested array size exceeds VM limit.	This error indicates you are attempting to upload an archive that is too large for the current limit (in GB). Check the content and size of the files or archives you are uploading to verify you are using the correct files.
Veracode Jenkins Plugin or Java API wrapper	I see this message: [16.01.11 14:28:39] java/net/HttpURLConnection.setFixedLengthStreamingMode(J)V Build step Upload and Scan with Veracode marked build as failure Finished: FAILURE	This message indicates that the Java version you are using is not Java 7 or later. The Veracode Jenkins Plugin and the Veracode Java API wrapper require Java 7 or later.
Veracode Azure DevOps Extension	I am receiving upload errors for my Azure DevOps builds.	To resolve the upload errors, you have these options: Before uploading to Veracode, add the folder containing the files you want to scan to a ZIP archive. The ZIP archive suppresses errors due to unsupported file types. After prescan, resolve any fatal errors: Review the prescan results to identify the modules that have fatal errors. Resolve the errors. Optionally, if you do not want to resolve the errors, you can: Remove the modules that have errors: Update your uploaded files in the Veracode Platform. Update the values for the include and exclude parameters in the uploadandscan.do call to specify which files to include or exclude from upload. Update the build settings in Azure DevOps to specify which files to include or exclude from upload. Start the analysis manually. If you have not added or deleted any modules since the last analysis that contained the fatal errors, the next automated analysis uses the same selected modules. Ensure your binaries are in the default location, or modify the default location system variable$(build.artifactstagingdirectory) if you require your files to be in a different location. For example, if your files have a different pathname and are in a bin folder, you can modify your system variable to look like this:$(build.sourcesdirectory)pathname/bin. Microsoft provides pipeline build steps for creating a folder with only the files that Veracode requires for scanning. See the Copy Files task and Delete Files task in the pipeline documentation on the Azure documentation.
Veracode Azure DevOps Extension	I selected the Veracode Scan Summary tab in Azure DevOps to view scan results and see the message Veracode is taking longer than expected to load.	Clear your browser cache. Then, select the Veracode Scan Summary tab again.
Veracode Pipeline Scan	I received an error code message.	Try these resolutions for each error code: - 401: Unauthenticated. The API credentials may be expired. If they are not expired, verify the API credential ID and key you use in the pipeline match the generated credentials. They cannot contain extra spaces. - 403: Unauthorized. Check that the user accounts have Security Lead, Creator, and Submitter roles. Ensure the API user account credentials have Upload and Scan API or Upload API - Submit Only roles. - 429: Throttled. The API credentials were submitted for more than six scans in the last one minute. Try again after a short delay. - -50x: Server side problems. This can be a problem with AWS or with Veracode services. Check the Veracode service status dashboards for details. For example, if the Identity Service is not working, then Pipeline Scan also does not work.
Veracode Pipeline Scan	I need to open a support case with Veracode Technical Support.	Provide this information to Veracode Technical Support: - Pipeline Scan version - Java version - Platform application name and the URL of the application - Build logs - Debug logs
Veracode Pipeline Scan	I see a PKIX error as a result of this SSL error: PIPELINE-SCAN ERROR: CREATE FAILURE: Error executing HTTP request. Error was: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target. PIPELINE-SCAN ERROR: The scan failed to complete: there are no results to analyze.	Review the instructions for importing SSL certificates.