Basic Continuous Integration (CI) scenario

The pipeline examples use BMC's plugins to implement the process and scenario as mentioned in the subsequent sections. They can be used to create a standardized approach for implementing a CI process for mainframe development. The scenarios and codes are based on requests and requirements from customers who have started implementing their own pipeline and have asked BMC for advice. Regardless of the tool in use to implement a CI strategy, the process we encounter or have helped implement for our customers, always looks similar to what we describe here.

Related topics

Developer-s-tasks

CI-pipeline-job

Pipelines

Continuous_Integration.png


The code we have shared to implement these process steps, shows BMC's example approach to these requirements. It does not necessarily reflect actual customer implementations and is considerably different from those implementations.

The Jenkins examples will help mainframe developers to familiarize themselves with Groovyand its concepts.

The Azure DevOps Pipeline example, and underlying Microsoft PowerShell scripts, illustrate that you are not limited to Jenkins when implementing a mainframe-based CI process.

 

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