CI/CD Jobs
The following topics describe job types for Continuous Integration and Continuous Deployment (CI/CD) services.
Ansible AWX Job
Ansible AWX jobs enable you to manage Ansible playbooks, inventories, and job scheduling.
To create an Ansible AWX job, see Creating a Job. For more information, see Control-M for Ansible AWX.
The following table describes the Ansible AWX job parameters:
Attribute |
Action |
Description |
---|---|---|
Connection Profile |
All |
Determines the authorization credentials that are used to connect Control-M to Ansible AWX, as described in Ansible AWX Connection Profile Parameters. Rules:
|
Action |
NA |
Determines one of the following actions to perform:
|
Job Template Name |
Launch Job Template |
Determines the name of an Ansible AWX job template that defines how a particular playbook is executed. If there are several templates with the same name, the job uses the first template found. |
Job Template ID |
Launch Job Template by ID |
Determines the ID of an Ansible AWX job template that defines how a particular playbook is executed. |
Workflow Template Name |
|
Determines the name of an Ansible AWX workflow template that defines a sequence of job templates and their relationships. |
Project Name |
Sync Project |
Determines the name of an Ansible AWX project that contains Ansible playbooks and related files. If there are several projects with the same name, the job uses the first project found. |
Project ID |
Sync Project by ID |
Determines the ID of an Ansible AWX project that contains Ansible playbooks and related files. |
Inventory |
|
Determines a collection of hosts or machines defined in Ansible AWX that is the target environment for job execution. |
Inventory Source |
Sync Inventory Source |
Determines a cloud provider or other source of hosts that Ansible AWX assigns to an inventory. |
Parameters |
|
Defines job template launch parameters such as inventory, credentials, job variables, and limit options to define how the playbook runs and which host it targets. Format: {"<param1>":<value1>,"<param2>":<value2>} (JSON format) |
Output Logs |
|
Determines whether the job returns a detailed execution record to Control-M. |
Status Polling Frequency |
All |
Determines the number of seconds to wait before checking the job status. Default: 15 |
Failure Tolerance |
All |
Determines the number of times the job tries to run before ending Not OK. Default: 15 |
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 job 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 |