Security¶
In this stage important security-relevant checks will be conducted.
This is to achieve a decent level of security for your application.
Stage Content¶
This stage comprises following steps which are activated depending on your use-case/configuration:
| step | step description | 
|---|---|
| checkmarxExecuteScan | Executes a Checkmarx scan | 
| detectExecuteScan | Executes BlackDuck Detect scans | 
| fortifyExecuteScan | Executes a Fortify scan | 
| whitesourceExecuteScan | Executes a WhiteSource scan | 
Stage Activation¶
This stage will be active if any one of the following conditions is met:
- Stage configuration in config.yml file contains entries for this stage.
- Any of the conditions are met which are explained in the section Step Activation.
Step Activation¶
For this stage no conditions are assigned to steps.
Additional Stage Parameters¶
| name | mandatory | default | possible values | 
|---|---|---|---|
| script | yes | 
- script- The common script environment of the Jenkinsfile running. Typically the reference to the script calling the pipeline step is provided with the- thisparameter, as in- script: this. This allows the function to access the- commonPipelineEnvironmentfor retrieving, e.g. configuration parameters.
Configuration of Additional Stage Parameters¶
The stage parameters need to be defined in the section stages of config.yml file.