Mainframe DevOps: Extend CI/CD to z/OS

Mainframe DevOps applies version control, automated build and test, and governed deployment to COBOL, PL/I, JCL, and Assembler applications on z/OS. The mainframe stage becomes one node in the pipeline you already run. Your orchestrator triggers the work, BMC AMI DevX Code Pipeline executes build, promotion, deployment, and audit on z/OS, and results return to the pipeline that called it. Source can live in Enterprise Git, in Code Pipeline, or in both.

BMC AMI DevX Code Pipeline integrates with Jenkins, Azure DevOps, and GitHub through DevOps Extensions. GitLab CI/CD and other orchestrators connect through REST APIs, command-line interfaces, and webhooks. Generate, Promote, Deploy, and Regress run on z/OS directly from the orchestrator you already use. The integration model is event-driven, so adding mainframe stages to a pipeline you already run does not require rebuilding it.

BMC AMI DevX Code Pipeline promotes changes through lifecycle stages such as development, QA, and production, enforcing approvals at each gate. Code Pipeline captures every promotion, approval, and deployment in one audit trail as it happens, and approvals can be issued from web or mobile. When a deploy goes wrong, Code Pipeline supports partial or full fallback, replacing the current production program with a valid previous version on demand.

Mainframe teams run the same sprint cadence and the same backlog as distributed teams. BMC AMI DevX Code Pipeline supports concurrent development, so multiple developers work on the same program at the same time without overwriting each other's work. Impact Analysis flags downstream effects before the merge. Developers work in VS Code or Eclipse through BMC AMI DevX Workbench. Forrester measured 50% faster developer onboarding and 33% faster code changes at organizations running Code Pipeline.

Migration runs as a controlled, incremental transition. Existing promotion models, approval paths, and lifecycle structure map into BMC AMI DevX Code Pipeline, and BMC Services provides migration support. Teams can shift build and deployment first and decide about source separately, keeping source in Code Pipeline or moving it to Enterprise Git. Migration can proceed application by application or release stream by release stream, so no single cutover date carries the whole portfolio.

Yes. BMC AMI DevX Code Pipeline operates as the source code manager for mainframe applications, with feature branching and a lifecycle view showing the status of every program at every level, including production. Code Pipeline interoperates with Git workflows where the rest of the organization works, so teams can adopt Git later or keep source where it is. Build, promotion, deployment, and audit run on z/OS the same way in either configuration.

BMC AMI DevX Code Pipeline generates CycloneDX JSON software bills of materials for COBOL, PL/I, JCL, and Assembler applications through a batch job teams schedule inside the pipeline they already run. The inventory covers program names and versions, copybooks, and called programs for the components Code Pipeline manages, and it refreshes as often as the job runs. Distributed CI/CD platforms generate SBOMs for containers and packaged artifacts and do not cover mainframe applications.