Before setting up a CI/CD pipeline with BMC AMI DevX Code Pipeline, make sure that the following components and configurations are in place:
| Category | Requirement |
| Code Pipeline setup | - Code Pipeline environment with defined lifecycle (DEV → QA → STG → PROD)
- A application configured and loaded with data in Code Pipeline. This guide uses the PLAY application, which comes with Code Pipeline
- Data set naming standards in place (Base, Site, Application datasets)
- Separate STC IDs for TEST versus PROD
|
| |
| |
| CI/CD environment | - CI/CD platform (for example, Jenkins, Azure DevOps, GitHub Actions, or GitLab CI/CD)
- CI/CD agents or runners with network access to the mainframe (HCI)
- Any orchestration tool that can run CLI commands or invoke REST APIs can integrate with Code Pipeline ( for example, Jenkins, Azure DevOps, GitHub Actions, GitLab CI/CD, or other custom orchestrators)
- User credentials (user ID and password or certificates) for the CI/CD pipelines to perform actions in Code Pipeline
- Secure credential storage configured in the orchestration environment (for example, Jenkins Credentials, Azure Service Connections, or GitHub Secrets)
|
| |
| |
| Workbench CLI and tools | Workbench CLI installed on CI/CD agents, which includes: - Code Pipeline CLI (IspwCLI) and SCM Downloader CLI (SCMDownloaderCLI)
- Total Test CLI (TotalTestFTCLI)
- Code Coverage CLI (CodeCoverageCLI)
|
| |
| |
| |
| Source control (Git integration) | Git repository set up for Total Test assets. (Optional) Git-to-Code Pipeline integration configured (ispwconfig.yml, path mappings, branch model). |
| |
| - (Optional) SonarQube server accessible
- SonarScanner installed on CI/CD agents
- SonarQube projects created & bound to Code Pipeline applications
- Quality gates defined in SonarQube
|
| |
| |
| |
| Webhooks and API access | - Configured Code Pipeline webhooks (promote/generate triggers)
- CES Personal Access Tokens (PATs) or certificate-based auth available
- Configured CSRF protection if you use Jenkins REST API triggers
|
| |
| |
| Mainframe and application environment | - Code Pipeline fully installed and configured
- Applications loaded and complete workflow implemented (including generate, promote, deploy, and approvals)
- Additional BMC AMI DevX tools installed and configured
- (Optional) Host Communication Interface (HCI) for access to DevX tools from outside the mainframe Total Test
- (Optional) Code Debug and Code Coverage
|
| |
| |
| |
| |
