While the PagerDuty Incident Trigger action makes sense to be a post-build action that is tied to the build status, I submit that a Change Event is a different animal. Pagerduty’s own docs describe them as:

service changes such as deploys, build completion, configuration updates, etc., providing contextual information that is critical during incident triage

https://support.pagerduty.com/docs/change-events

Based on this definition (and use cases I would like to support related to deployment start/end change events), it would be extremely helpful to implement the ChangeEvent feature as a normal build step that can be repeated as many times as necessary during the course of the build. This is already possible with the pipeline implementation. I would love to see this implemented for the classic freestyle job type as well.

See #45 and #46 for related functionality I've posted. These issues resolved together might provide a nice 0.7.x release.

This change would allow for the following screenshot, and bring feature parity with the pipeline implementation.