Tool configurations

The scenarios covered by the primary pipelines, the other pipeline examples, and more generally the use of the BMC's and third party plugins, require certain configurations and settings, both within Jenkins and within other tools provided by BMC.

Related topics

Introduction-to-Jenkins-Plugins

Jenkins-configuration

Using-Jenkins-Plugins

CES-Webhook-Configuration

CES-Personal-Access-Tokens

BMC AMI Common Enterprise Services

Next to serving as web application server for BMC's web based tools such as iStrobe or the Code Pipeline web interface, BMC AMI Common Enterprise Services (CES) provides a set of services that allow interfacing with BMC tools outside the mainframe. For Jenkins and CI/CD these are Code Pipeline Webhooks and CES Credentials Tokens.

Code Pipeline Webhooks

Code Pipeline allows registering webhooks to use events in the Code Pipeline software life cycle to trigger events outside of Code Pipeline like triggering a Jenkins pipeline. CES may be used as one source to define and register webhooks for Code Pipeline. Both primary pipelines make use of such webhooks defined in CES. Refer to the Webhooks** section in the BMC AMI Common Enterprise Services online help for setting up Code Pipeline webhooks and the parameters that may be passed from Code Pipeline to the webhook. 

Definition of a webhook used in the examples.

CES credentials tokens

The BMC plugins (and other operations) make use of credential tokens defined in CES. These tokens store mainframe TSO user id and password and allow authentication against the mainframe without using clear text credentials within script code. 


 

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