Control-M for Jenkins

Jenkins enables you to automate building, testing, and deploying code for repetitive tasks in the software deployment process.

Control-M for Jenkins enables you to do the following:

• Execute Jenkins pipelines.

• Manage Jenkins credentials in a secure connection profile.

• Connect to any Jenkins endpoint.

• Introduce all Control-M capabilities to Control-M for Jenkins, including advanced scheduling criteria, complex dependencies, resource pools, lock resources, and variables.

• Integrate Jenkins jobs with other Control-M jobs into a single scheduling environment.

• Monitor the status, results, and output of Jenkins jobs.

• Attach an SLA job to the Jenkins jobs.

Setting up Control-M for Jenkins

This procedure describes how to deploy the Jenkins plug-in, create a connection profile, and define a Jenkins job in Control-M SaaS and Automation API.

Before You Begin

• Verify that Jenkins 2.387.1 or higher is installed.

• Verify that Java is installed, as described in Control-M External Java Installation.

• Verify that Automation API is installed, as described in Setting Up the API.

• Verify that Agent version 9.0.21.080 or higher is installed.

Begin

1. Do one of the following:

   • Install: Run one of the following provision image commands:

     • Linux: ctm provision image Jenkins_plugin.Linux

     • Windows: ctm provision image Jenkins_plugin.Windows

   • Upgrade: Run the following command:

     ctm provision agent::update

2. Create a Jenkins connection profile in Control-M SaaS or Automation API, as follows:

   • Control-M SaaS: Create a Centralized Connection Profile with Jenkins Connection Profile Parameters

   • Automation API: Connection Profile:Jenkins

3. Define a Jenkins job in Control-M SaaS or Automation API, as follows:

   • Control-M SaaS: Create a Job with Jenkins Job parameters

   • Automation API: Job:Jenkins

Change Log

The following table provides details about changes that were introduced in new versions of this plug-in:

Plug-in Version	Details
1.0.02	Added HTTP Codes, Rerun Interval, and Attempt Reruns parameters to the connection profile to rerun an execution step with an HTTP code
1.0.01	Added Fetch Console Logs to job definition.
1.0.00	Initial version