Setting up the pipeline job


The pipeline job itself is defined within Jenkins by creating a new pipeline job. It is important to make sure that the resulting job uses parameters by selecting the `This project is parameterized' check box.


SettingUpPipelineJob_1.png

Pipeline parameters

Successively add the following string parameters (default values are used in the examples).

SettingUpPipelineJob_2.png
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 Pipeline Stream Name

ISPW_Application

Code Pipeline Application

ISPW_subApplication

Code Pipeline SubApplication

ISPW_Release

Code Pipeline Release Name

ISPW_Assignment

Code Pipeline Assignment

ISPW_Src_Level

Code Pipeline Level the promote has been started from

ISPW_Owner

Code Pipeline Owner 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

CES Token, 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


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*