Skip to main content

Implementing pipeline actions

Common Back-end Scripts

Popular choices for continuous integration/continuous delivery (CI/CD) pipeline orchestration include Azure Pipelines, Github Actions, Gitlab CI, and Jenkins. Each orchestrator has its specific way of defining the configurations to coordinate pipeline actions. For instance, Jenkins has its Jenkinsfile, and GitLab CI has its .gitlab-ci.yml file.

To help provide a consistent CI/CD pipeline experience regardless of your selected pipeline orchestrator, the Dependency Based Build (DBB) community repository provides a set of Common Back-end Scripts for pipeline implementations. These scripts cover orchestration tasks throughout the CI/CD pipeline, and can be run from any pipeline orchestrator by including them in the orchestrator's configuration as shell script invocations. You can learn more about how to use these Common Back-end Scripts to simplify your pipeline configuration and setup in the Common Back-end Scripts Readme.

The following video demonstrates an implementation of the Common Back-end Scripts using an Azure DevOps (ADO) pipeline.

Specific guides for each orchestrator

The following guides for the common pipeline orchestrators may help you get started with implementing your CI/CD pipeline. Although written before the creation of the Common Back-end Scripts, these guides can be used to integrate the Common Back-end Scripts into the specific orchestrators.

Note: These guides cover commonly-selected combinations of tools for the different CI/CD pipeline components, but they are intended as examples and are therefore not all-inclusive. If you do not see the specific technology or combination of tools your enterprise has selected, that does not necessarily mean it cannot align with our guidance. For most tools being used elsewhere, you can integrate them into the pipeline as long as they are compatible with z/OS® application development and bring value to your enterprise.

Azure Pipelines

GitHub Actions

GitLab CI

Jenkins