Note About Rescans Performed by v2.0 and Later Plugins

Scan agent v2.0 and later plugins support alias names. An alias name is used to uniquely identify a remote scan agent for a given project as well as differentiate the codebase scanned via the agent from other project codebase files. Alias names are unique within a given project and cannot be shared across multiple scan agents.

In general, a rescan performed by a v2.0 or later scan-agent plugin uses the same alias and hostname that the previous scan used. However, in a dynamic host environment (such as is supported by CI tools, where hosts are dynamically allocated as needed for cloud or linked builds), the instance on which a rescan is run might be different from the instance used in the previous scan, in turn causing the rescan to fail.

Therefore, for those v2.0 and later plugins used for Engineering platforms that support dynamic host environments, you must provide a value for the new “host” property in the plugin configuration. This value should be a user-defined name for the host instance on which the scan will be run. The value will then remain the same even if the instance used for a rescan is different from the one used in the previous scan.

This property is currently available for the Jenkins, Bamboo, Azure DevOps, and the generic scan-agent plugins.