Jenkins : PagerDuty Plugin

Features

• Trigger incidents on various job statuses Success/Failure/Aborted/Unstable/Not_Built
• Trigger incidents based on number of consecutive build results
• Automatically Resolve incidents when job is back to normal
• Pipeline compatible
• TokenMacro consumer (TokenMacro - adds reusable macro expansion capability)

pipeline example:

if resolve == false, the pagerduty triggers an incident and returns the incidentKey

pagerduty(resolve: false, serviceKey: "$SERVICE_KEY", incidentKey: "$INCIDENT_KEY", incDescription: "pipeline test incident", incDetail: "pipeline test")

Requirements

• Jenkins version 1.580.1 or newer is required.
• PagerDuty account (you can create a free developer account here)

Configuration

Version History

Version 0.4.1 (Mar 12, 2019)

• Add TokenMacro support
• Bug fixes
• Code refactor

Version 0.3.0 (Jan 31, 2017)

• Pipeline compatible
• Code refactor

Version 0.2.6 (June 20, 2017)

• Bug fixes
• PagerDuty v2 compatibility (migrating from square PD utility to dikhan's PD client)

Version 0.2.5 (March 10, 2017)

• Bug fixes

Version 0.2.4 (March 30, 2016)

• Allow automatic resolution of the incident on BACK-TO-NORMAL (from not success to success)

Version 0.2.3 (March 09, 2016)

• Bug fixes

Version 0.2.2 (January 03, 2016)

• Allow triggering alert in all job statuses (SUCCESS/FAILED/ABORTED/UNSTABLE/NOT_BUILT)
• Allow using multiple service keys for different job

Version 0.2.1 (December 08, 2015)

• Allow using Environment Variables for config

Version 0.2.0 (September 26, 2015)

• Initial public release