Automating Db2 schema changes in CI/CD projects and pipelines
Related topics
By automating schema deployment, you accelerate software delivery with BMC AMI DevOps for Db2.
The benefits include:
- Reducing deployment time from days to minutes.
- Minimizing manual errors.
- Enabling more effective team collaboration across development and operations.
- Improving compliance and auditability.
Workflow for automating schema change deployment
| Task | Product | Role | Action | Reference |
|---|---|---|---|---|
| 1 | Jenkins, Azure DevOps, GitHub Actions, or GitLab CI/CD | DevOps engineer | Configure the project or pipeline to trigger schema change deployment | Quick start to automating Db2 schema changes |
| 2 | BMC AMI DevOps for Db2 | Application developer | Define inputs for the developer's schema definitions | Using Jenkins UI or UC YAML configuration and pipeline files: |
| 3 | BMC AMI DevOps for Db2 | Application developer, Db2 DBA | Review the impact analysis and approve changes | Analysis impact report |
| 4 | BMC AMI DevOps for Db2 | Application developer | Submit JCL via the project or pipeline to apply schema changes | Running JCL:
|
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*