Skip to Content

Introduction

In modern IT, DevOps is more than a set of tools-it’s a culture of collaboration that brings together development, operations, security, and business teams to deliver software faster and with higher quality. While distributed platforms have embraced DevOps practices for years, mainframe systems have often been left behind, creating gaps in delivery speed, tooling, and culture.

With the BMC AMI DevX Code Pipeline product, enterprises can now bridge this gap by seamlessly integrating mainframe development into modern CI/CD pipelines. Instead of being treated as a separate legacy platform, mainframe applications now participate in the same DevOps pipeline, tools, and governance as the rest of the enterprise.

This document provides practical steps and examples for integrating Code Pipeline with CI/CD tools such as Jenkins, Azure DevOps, GitHub Actions, Bitbucket, and GitLab. It also demonstrates how to extend pipelines with the BMC AMI DevX Total Test product for automated regression and unit testing, and with SonarQube for enforcing quality gates and code analysis.

Key benefits

  • Unified workflow for mainframe and distributed code
  • CI/CD readiness when integrated with supporting frameworks such as Total Test or other automated testing solutions, enabling automated builds, testing, and deployments through Code Pipeline
  • Flexible orchestration using Jenkins, GitHub Actions, Azure DevOps, or GitLab
  • Two integration options: Code Pipeline native repository and Git with Code Pipeline (hybrid)
  • Integrated quality assurance with Total Test, Code Coverage, and SonarQube
  • Improved collaboration and consistency across development teams

Purpose of the DevOps pipeline

The following diagram displays an example of the high-level CI/CD pipeline stages for Code Pipeline:

purpose.png

The purpose of a pipeline such as in this example is to automate the quality assurance process, especially by using tools such as SonarQube to implement quality gates and to use their results to automate the process for deciding whether a code change may proceed further in the lifecycle, or a revision is required.

While pipelines can serve different purposes at different stages of the lifecycle or for different applications, a workflow like the above is very common in non-mainframe development.

When using Git for mainframe development, the following diagram illustrates the minimal workflow required:

purpose 2.png

 

 

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

Integrating BMC AMI DevX Code Pipeline into CI/CD workflows