Jenkins

Learn how to connect Jenkins to ZigiOps. Supported versions, authentication methods, connected system configuration, and available integration templates.

What is Jenkins integration in ZigiOps?

Jenkins is an automation server used for continuous integration (CI) and continuous delivery (CD). It enables development teams to automate builds, testing, and deployment pipelines.

ZigiOps enables secure, API-based integration between Jenkins and ITSM, ITOM, DevOps, and monitoring systems. Using ZigiOps, Jenkins jobs, builds, and pipeline events can be synchronized with external platforms to support automated workflows and cross-team collaboration.

With ZigiOps, Jenkins can:

Trigger ITSM incidents when builds fail
Synchronize pipeline execution status with change management systems
Update DevOps issues based on deployment progress
Participate in event-driven CI/CD workflows
Enable bidirectional synchronization between Jenkins and external platforms

The integration is fully customizable and does not require custom scripts or plugins.

Which Jenkins versions are supported?

Please note that using a supported version is mandatory. Jenkins must expose a functional REST API and allow authenticated access.

Are there any environmental prerequisites for Jenkins?

Confirm the prerequisites of the corresponding integration template before continuing further, as some templates may not require all environmental prerequisites.

Jenkins Requirements:

Jenkins instance accessible from ZigiOps
REST API enabled
Valid Jenkins user account
API Token generated (recommended for secure authentication)

Network and Connectivity Requirements:

HTTPS access to the Jenkins server
If Jenkins is hosted on-premises behind a firewall:
- Install the ZigiOps agent within the customer environment
- Ensure outbound encrypted communication over TLS 1.2

ZigiOps supports secure communication via HTTPS and encrypted protocols.

How do I connect Jenkins to ZigiOps?

Jenkins - Connected System Configuration

Open Jenkins connected system setup

Navigate to Connected Systems > Add New System > Jenkins.

Configure the connection parameters

Configure the following parameters:

Server URL Input the full base URL of your Jenkins instance. Example: https://jenkins.company.com

Authentication Type Select the authentication method.

Username Input the Jenkins username.

API Token / Password Input the generated Jenkins API token (recommended for secure authentication).

Proxy Settings Enables the usage of a proxy server, if required.

Save the system

Examine the settings and, if they are correct, click Save to store the system.

Once saved, Jenkins becomes available for use in ZigiOps integration templates.

What are the most common Jenkins integration use cases?

Use case 1: CI failure to incident automation

When a Jenkins build fails, ZigiOps can automatically create an incident in an ITSM platform (such as ServiceNow, Ivanti, or Jira), enabling faster resolution and centralized service management.

Use case 2: Deployment-driven change updates

Pipeline execution results in Jenkins can update change requests in external ITSM systems, ensuring accurate deployment tracking.

Use case 3: DevOps visibility across tools

Jenkins build and pipeline data can be synchronized with issue tracking systems, ensuring development and operations teams share consistent, real-time information.