Jenkins Changes Integration Guide | PagerDuty

Jenkins + PagerDuty Integration Benefits

Create PagerDuty Change Events from Jenkins post-build events.

How it Works

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

Requirements

  • 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.

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 a new integration. Enter an Integration Name in the format Service-Name-Jenkins-Changes, select Jenkins CI from the Integration Type dropdown and click Add Integration.
  3. On the next screen in the Integrations list, find the integration you just created, copy the Integration Key and keep it in a safe place for future use.

In Your Jenkins Plugin

  1. Add a post-build action to your Jenkins plugin for PagerDuty Change Events and paste the PagerDuty Integration Key in the Service Integration Key field. Select the build result(s) that should create change events and then click Save.

Send Change Events

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

Updated 7 months ago


Jenkins Changes Integration Guide | PagerDuty


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.