Gary (Community Member) asked a question.
I am running into problems integrating the Veracode scan file upload into our build pipelines. We have the service connection set up in Azure DevOps, the files are being dropped where they need to be, and the Veracode Upload extension is set correctly as far as I can tell.
The build pipeline runs, gets to the extension, the extension runs, and... nothing (see below)? That's what it looks like to me, anyways. I don't see anything being uploaded to our Veracode account for scanning.
I have verified that the API ID, API key, application name, service connection, and file location are correct. I even uploaded the zipped files manually for scanning and results are generated. What am I missing? Given a lack of debugging information, what else should I check?
.png){kind=logo}
This issue is resolved.
The Azure DevOps Build Agent didn't have Java installed on the self-hosted machine. The machine was not restarted after the installation so the settings did not "take" yet. The upload began working after the machine was restarted since it was able to find the Java executable.
That being said, the extension was very misleading. It would've been extremely helpful for the extension to throw an error and display an error message rather than completing without errors.