Add the Veracode Azure DevOps Extension to an Azure DevOps or TFS Release Pipeline
You can configure the Veracode Azure DevOps Extension to add the Veracode Upload and Scan task and the Veracode Flaw Importer task to a release pipeline in Azure DevOps or Team Foundation Server (TFS).
To complete this task:
In your Azure DevOps or TFS project, select the Release tab.
Create a new release and enter the definition name.
On the Definition page, select the Environment tab and configure the Veracode Upload and Scan or Veracode Flaw Importer tasks. If you want to view a summary report of scan results, you must add the Veracode Upload and Scan task.note
The build object is not available in the release pipeline. Therefore, if you intend to use the Veracode Upload and Scan task in the release pipeline, you must enter the scan name manually. If you do not enter it manually, the scan name variable does not convert to text and the build name appears as
Save the definition and select Release > Create Release.
For the Veracode Flaw Importer task, if you are using TFS, configure these variables:
For TFS 2017 or higher, set
For TFS 2015, configure these variables:
username: enter your Windows username.
password: enter your Windows password.
domain: enter the Windows domain.
On the Release tab, select the release you just created.
For the Veracode Upload and Scan task, in the Environments section, select the environment that contains the task.
From the Actions menu, select Deploy to start the build in the release pipeline.
After the scan is complete, in your build definition, you can select the Veracode Scan Summary tab to view the scan results.
For Azure DevOps and TFS 2018 Update 2 or later, if you do not include the Veracode Upload and Scan task in your build definition, you do not see the Veracode Scan Summary tab in the build summary. For earlier versions of TFS, the Veracode Scan Summary tab shows a status message explaining why there are no results.