Jenkins Changes Integration Guide | PagerDuty

Configure the Jenkins Changes | PagerDuty integration

Jenkins Changes + PagerDuty Benefits

Requirements

📘

Availability

This integration is available with our PagerDuty AIOps add-on. If you would like to sign up for a trial of PagerDuty AIOps features, please read PagerDuty AIOps Trials.

  • In PagerDuty: This integration requires a Manager base role or higher to configure.
  • In Jenkins: This integration requires administrator permissions to install the Jenkins PagerDuty plugin.

How it Works

  • Jenkins build events will be sent to PagerDuty, creating change events on integrated services.

Integration Walkthrough

Install the Jenkins Plugin

  1. Install the Jenkins PagerDuty plugin.

In PagerDuty

  1. Navigate to Services Service Directory and click the name of the service that you would like to add the integration to.
  2. Select the Integrations tab and click Add an integration.
  3. Search for and select Jenkins CI, and click Add.
  4. From the list of integrations, click to the right of Jenkins CI.
A screenshot of the PagerDuty UI showing the Jenkins CI integration

Jenkins CI integration

  1. In the field Integration Key, click to copy the integration key to your clipboard. Keep this key in a safe place for use in the next section.

In Your Jenkins Plugin

  1. From your Jenkins dashboard, select your desired job Configure Post-build Actions tab.
  2. From the Add post-build action dropdown, select PagerDuty Change Events.
A screenshot of the Jenkins UI showing where to select "PagerDuty Change Events"

Select "PagerDuty Change Events"

  1. Paste the PagerDuty integration key from the previous section into the Integration Key field and select the build result(s) that you would like to create change events.
A screenshot of the Jenkins UI detailing post-build Actions

Post-build Actions

  1. Click Save.

Using the Integration

Once configured, build events specified in step 9 (above), will be sent to PagerDuty as change events.


Learn more