Skip to Content

Jenkins Connector

Summary

The Jitterbit Harmony Jenkins Connector establishes access to Jenkins.

The Jenkins connector provides an interface for creating a Jenkins connection, the foundation used for generating instances of Jenkins activities. These activities, once configured, interact with Jenkins through the connection.

The Jenkins connector is accessed from the design component palette's Connections tab (see Design Component Palette).

Connector Overview

This connector is used to first configure a Jenkins connection. Activity types associated with that connection are then used to create instances of activities that are intended to be used as sources (to provide data in an operation) or targets (to consume data in an operation).

Together, a specific Jenkins connection and its activities are referred to as a Jenkins endpoint:

Jenkins activity types

  • Stop Job: Stops a job in a Jenkins automation server and is intended to be used as a target in an operation.

  • Start Job: Starts a job in a Jenkins automation server and is intended to be used as a target in an operation.

  • Delete Job: Deletes a job from a Jenkins automation server and is intended to be used as a target in an operation.

  • Get Job: Retrieves a job from a Jenkins automation server and is intended to be used as a source in an operation.

Note

This connector is a Connector SDK-based connector, which may be referred to by Jitterbit when communicating changes made to connectors built with the Connector SDK.

Prerequisites and Supported API Versions

The Jenkins connector requires the use of an agent version 10.1 or later. These agent versions automatically download the latest version of the connector when required.

The Jenkins connector uses the Jenkins Remote Access API.

Troubleshooting

If you experience issues with the Jenkins connector, these troubleshooting steps are recommended:

  1. Ensure the Jenkins connection is successful by using the Test button in the configuration screen. If the connection is not successful, the error returned may provide an indication as to the problem.

  2. Check the operation logs for any information written during execution of the operation.

  3. Enable operation debug logging (for Cloud Agents or for Private Agents) to generate additional log files and data.

  4. If using Private Agents, you can enable connector verbose logging for this connector using this specific configuration entry of logger name and level:

    <logger name="org.jitterbit.connector.jenkins" level="DEBUG"/>

  5. If using Private Agents, you can check the agent logs for more information.