CI/CD Jobs
The following topics describe job types for Continuous Integration and Continuous Deployment (CI/CD) services.
Azure DevOps Job
Azure DevOps enables you to efficiently plan, track, manage work, version control your code, automate build and deployment pipelines, and conduct comprehensive testing, within a single, integrated, cloud-based environment.
To create an Azure DevOps job, see Creating a Job. For more information, see Control-M for Azure DevOps.
The following table describes the Azure DevOps connection profile parameters.
|
Attribute |
Description |
|---|---|
|
Connection Profile |
Determines the authorization credentials that are used to connect Control-M to Azure DevOps, as described in Azure DevOps Connection Profile Parameters. Rules:
|
|
Project Name |
Defines the name of the project in Azure DevOps that includes the required pipelines database catalog that the job points to when executing the query. |
|
Actions |
Determines one of the following actions to perform.
|
| Pipeline ID |
Determines the ID number of the pipeline to execute, as defined in Azure. |
| Repository path |
Defines the branch or ref to trigger the pipeline. "refs/heads/release/MAIN |
| Variables |
Defines the variables when the pipeline runs, in JSON format, as shown below: Copy
|
| Parameters |
Defines parameters that are passed to the pipeline, in the following format: "param1": "value1", "param2": "value2" |
|
Stages to Skip |
Defines an array of stage names to skip when the pipeline runs. "Test", "Deploy" |
|
Show Build Logs |
Determines whether to show additional logs. |
|
Status Polling Frequency |
Determines the number of seconds to wait before Control-M checks the status of the job or the job's output. Default: 10 |
|
Failure tolerance |
Determines the number of times to check the job status before the job ends Not OK. Default: 3 |
Jenkins Job
Jenkins enables you to automate building, testing, and deploying code for repetitive tasks in software deployment process.
To create a Jenkins job, see Creating a Job. For more information about this plug-in, see Control-M for Jenkins.
The following table describes the Jenkins job parameters.
|
Attribute |
Description |
|---|---|
|
Connection Profile |
Determines the authorization credentials that are used to connect Control-M to Jenkins, as described in Jenkins Connection Profile Parameters. Rules:
|
|
Pipeline Name |
Determines the name of Jenkins pipeline. |
|
Add Parameters |
Enables you to add parameters for further connection profile configuration. |
|
Parameters |
Defines the dynamic variables for the Jenkins job ( as key:value pairs), which control how the job executes. |
|
Add Branch Name |
Enables you to add a branch to a Jenkins Multibranch Pipeline. |
|
Branch Name |
Defines the branch name. |
|
Status Polling Frequency |
Determines the number of seconds to wait before Control-M checks the status of the job or the job's output. Default: 20 |
|
Failure tolerance |
Determines the number of times to check the job status before the job ends Not OK. Default: 2 |
