Setting up the pipeline job
Pipeline parameters
Successively add the following string parameters (default values are used in the examples).
The parameters in the first set are specific to the individual execution of the pipeline and get passed by the CES-Webhook-Configuration.
Name | Description |
|---|---|
ISPW_Stream | Code PipelineStream Name |
ISPW_Application | Code PipelineApplication |
ISPW_subApplication | Code PipelineSubApplication |
ISPW_Release | Code PipelineRelease Name |
ISPW_Assignment | Code PipelineAssignment |
ISPW_Src_Level | Code PipelineLevel the promote has been started from |
ISPW_Owner | Code PipelineOwner User ID |
The second set of parameters are installation specific settings, reference tokens, and other IDs that have been defined during the configuration phase in Jenkins. They allow setting up different jobs, using different values for the configuration settings (if required) but using the same script for execution. To determine the appropriate values to use, refer to the description of the pipeline parameters.
Name | Description |
|---|---|
CES_Token | CESToken, will be required by the XL Release Template |
Jenkins_CES_Token | Jenkins credentials ID storing the CES Token, will be used for Code Pipeline operations |
HCI_Conn_ID | Jenkins internal ID for HCI Connection |
HCI_Token | Jenkins credentials ID TSO logon to HCI |
CC_repository | Code Coverage Repository - Check with your BMC AMI DevX Code Coverage administrator for the name to use |
Git_Project | Github (or any Git based repository) project used to store the Total Test Projects |
Git_Credentials | Jenkins credentials ID for logon to Git server |