# Configuring a Pipeline from a Shared Library

# Setting up the pipeline job

The job itself is defined via the usual way of creating a new pipeline job. It is important, though, to make sure that the resulting job uses parameters by checking the This project is parameterized box,

# Defining parameters

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

The parameters in this first set are specific to the individual execution of the pipeline and get passed by the ISPW Webhook.

# Loading the script from a shared library

To tell Jenkins to execute a pipeline from a shared library, you need to add code like the following to the Pipeline script definition:

The example uses

@Library('RNU_Shared_Lib@Dev') _
Mainframe_CI_Pipeline_from_Shared_Lib(
    ISPW_Stream         :"${ISPW_Stream}",                          // ISPW Stream
    ISPW_Application    :"${ISPW_Application}",                     // ISPW Application
    ISPW_Release        :"${ISPW_Release}",                         // ISPW Release
    ISPW_Assignment     :"${ISPW_Assignment}",                      // ISPW Assignment
    ISPW_Container      :"${ISPW_Container}",                       // ISPW Container (Set)
    ISPW_Container_Type :"${ISPW_Container_Type}",                  // ISPW Container Type (2 for Set)
    ISPW_Src_Level      :"${ISPW_Src_Level}",                       // ISPW Level the promote worked from
    ISPW_Owner          :"${ISPW_Owner}",                           // ISPW User doing the promote
    CES_Token           :'xxxx',
    HCI_Conn_ID         :'xxxx',
    HCI_Token           :'xxxx',
    CC_repository       :'xxxx',
    Git_Project         :'xxxx',
    Git_Credentials     :'xxxx'
    )

where

• @Library('RNU_Shared_Lib@Dev') _ refers to the name of a Shared Library, with @Dev in this example referring to the Dev branch of the underlying GitHub repository. The trailing _ is required by Jenkins.
• Mainframe_CI_Pipeline_from_Shared_Lib refers to the name of the .groovy file in the vars folder of the GitHub repository, containing the pipeline code
• Within the brackets (...) parameters are passed to the pipeline script. Mainframe_CI_Pipeline_from_Shared_Lib expects a groovy Map, containing the following key:value pairs.

The parameters in this first set are specific to the individual execution of the pipeline. The values are the parameters defined as pipeline parameters). The syntax "${parameter}" ensures that the value passed to this parameter is taken as a value in the Map.

The second set of parameters is installation specific and references tokens and other IDs that have been defined during the configuration phase. To determine the appropriate values to use, refer to the description of the pipeline parameters.

Usually, these parameters will be installation specific rather than pipeline job or execution specific. Future versions of the example will take care of this and move these parameters to configuration files.