Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Wiki Markup

Allows users to trigger postbuild incidents via PagerDuty


  • 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")



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)