Integration Directory
SaaS Application

Jenkins

Jenkins is an open-source automation server that enables teams to build, test, and deploy software through continuous integration and continuous delivery pipelines. Integrating Jenkins with Harmony brings your pipeline events and build failures directly into your IT service management workflow, reducing the time between issue detection and resolution. This connection gives your teams unified visibility into deployment health alongside incidents, changes, and other operational data.

Capabilities

  • Automated Incident Creation: Automatically generate Harmony incidents when Jenkins builds fail or pipelines encounter errors.
  • Change Request Synchronization: Link Jenkins deployment events to Harmony change requests to maintain a complete and auditable change history.
  • Pipeline Status Monitoring: Surface real-time Jenkins build and pipeline status within Harmony dashboards for centralized operational visibility.

What Harmony does with Jenkins

Connecting Jenkins lets employees run approved jobs and check build outcomes without opening the Jenkins console. Harmony reads your available jobs and pipeline status, so CI/CD steps slot into support and operations workflows. Teams get self-service provisioning and automated remediation, routed to the right Jenkins instance.

Data synced

  • Available jobs and pipeline definitions
  • Job execution status and build results
  • Build logs for workflow context
  • Instance targeting, so steps route to the right Jenkins server

Actions available

  • Trigger a Jenkins job directly from a workflow or agent step
  • Pass custom parameters to a job at trigger time
  • Route actions across environments, such as staging versus production

Real-world use cases

Self-service provisioning: An engineer runs an approved provisioning job from Slack, and Harmony passes the right parameters and returns the result.

Automated remediation: When a ticket is resolved, a workflow triggers a Jenkins job to redeploy or restart a service.

Multi-environment routing: A single workflow targets staging or production Jenkins instances depending on the request.

FAQ

Trigger Jenkins jobs and check build results from Slack or Teams, turning CI/CD into self-service. Connecting Jenkins lets employees run approved jobs and check build outcomes without opening the Jenkins console.