Veracode Integrations Release Notes

Veracode Release Notes

February 14, 2020

Veracode Greenlight for IntelliJ Supports IntelliJ IDEA 2019.3
Veracode Greenlight for IntelliJ version 1.5.1 adds support for IntelliJ IDEA Ultimate and Community 2019.3.

February 12, 2020

Veracode Jenkins Plugin Removes Basic Authentication
The Veracode Jenkins Plugin version 20.2.6.1 removes basic authentication. Basic authentication consists of only a username and password. You must now use Veracode API ID and key authentication. Any custom integration scripts must also include HMAC signing.

January 31, 2020

Veracode Static for Eclipse Supports Eclipse 2019-09
Veracode Static for Eclipse version 3.4.0 replaces the Veracode Eclipse Plugin. This version adds support for Eclipse 2019-09. It also adds support for Java Runtime Environment (JRE) 11 and 13.

You can no longer use basic authentication. Basic authentication consists of only a username and password. You must now use Veracode API ID and key authentication. Any custom integration scripts must also include HMAC signing.

January 24, 2020

Veracode Static for IntelliJ Supports IntelliJ IDEA 2019.3
Veracode Static for IntelliJ version 3.0.0 replaces the Veracode IntelliJ Plugin. This version supports IntelliJ IDEA Ultimate and Community 2017.x to 2019.3. It also adds support for Java Runtime Environment (JRE) 11 and 13.

You can no longer use basic authentication. Basic authentication consists of only a username and password. You must now use Veracode API ID and key authentication. Any custom integration scripts must also include HMAC signing.

January 23, 2020

Updated Veracode Integration for Jira
The Veracode Integration for Jira version 3.22.0 includes these updates:
  • Removes support for basic authentication. Basic authentication consists of only a username and password. You must now use Veracode API ID and key authentication. Any custom integration scripts must also include HMAC signing.
  • Enhances Jira logging, so that you can more easily read the logs.
  • Improves the performance of importing findings from the Veracode Platform to Jira using custom fields.

January 17, 2020

Veracode Static for Visual Studio Supports Visual Studio 2019
Veracode Static for Visual Studio version 4.0.0.1 replaces the Veracode for Visual Studio Extension. This version supports Visual Studio 2015, 2017, and 2019. In Visual Studio 2015 and 2017, the name of the top-level Veracode menu is now Veracode Static. In Visual Studio 2019, the Veracode Static menu appears under the Extensions menu.

You are required to configure an API credentials file, which you use to provide your Veracode API ID and key credentials to Veracode Static for Visual Studio.

January 8, 2020

Updated Veracode Integration for Jira Cloud
The Veracode Integration for Jira Cloud version 3.2.0 includes these updates:
  • Adds a new Veracode Integration Severity Mappings page in the Jira Cloud interface for mapping severities from the Veracode Platform to your customized priorities in Jira Cloud.
  • On the Veracode Integration Field Mapping page in the Jira Cloud interface, the Veracode Platform column adds these new options:
    • A Description (overwrite) option to have the content from a selected Veracode Platform field overwrite the Description field in Jira Cloud upon import. If the selected Veracode Platform field is empty, the mapping erases the contents of the Description field in Jira Cloud.
    • An option for mapping Veracode SCA component paths.
  • Removes basic authentication. Basic authentication consists of only a username and password. You must now use Veracode API ID and key authentication. Any custom integration scripts must also include HMAC signing.

December 19, 2019

New Veracode Greenlight for Visual Studio
The new Veracode Greenlight for Visual Studio version 1.0.0 supports Visual Studio 2019. The Veracode Greenlight menu appears under the Extensions menu in the Visual Studio interface. In previous versions of Visual Studio, the Veracode Greenlight menu is a top-level menu.

You are required to configure an API credentials file, which you use to provide your Veracode API ID and key credentials to Veracode Greenlight for Visual Studio.

December 11, 2019

Updated TeamCity Plugin
The Veracode TeamCity Plugin version 2.0.0 includes the following updates:
  • Adds support for TeamCity versions 2018.2 and 2019.1.
  • Removes basic authentication. Basic authentication consists of only a username and password. You must now use API ID and key authentication. Any custom integration scripts must also include HMAC signing.

December 7, 2019

New Video - Working with Scan Results Using the Veracode Visual Studio Extension
This video shows you how to download, import, and view Veracode scan results using the Veracode Visual Studio Extension. You can also learn how to mitigate findings discovered during the scan in Visual Studio.
New Video - Working with Scan Results Using the Veracode IntelliJ Plugin
This video shows you how to download, import, and view Veracode scan results using the Veracode IntelliJ Plugin. You can also learn how to mitigate findings discovered during the scan in IntelliJ.

December 5, 2019

Azure DevOps Extension Adds Option to Fail Build if Scan Fails
The Veracode Azure DevOps Extension version 2.9.0 adds a new option for configuring a pipeline build to fail if the Upload and Scan build step fails. By default, if the Upload and Scan build step fails, the pipeline build continues.