Issue Summary

Several issues related to the Opsgenie/CircleCI integration have been raised - listed below:

1) The integration documentation references using a deprecated version of webhooks no longer available in CircleCI

2) There looks to be an orb for use in current CircleCI implementations:

• CircleCI orb registry
• Opsgenie orb github repo

This works, partially - about half of the payload is parsed into the dynamic fields accessible in the integration, but many are not. Also - it is unclear how to configure this orb to notify for failed builds. This method is not listed on our integration documentation - but if it's intended to be used it would be good to add steps to configure there.

3) There is a v2 of CircleCI webhooks - this may be a preferable option in the end - but as the integration is set up now none of the payload fields are mapped over to Opsgenie dynamic fields.

Steps to Reproduce

N/A

Expected Results

Fully functional integration with CircleCI

Actual Results

Partial functionality - using orbs, successful builds post to OG with some of the integration's expected data, but not all. Using the new webhook - successful and failed builds will post, but none of the payload data is mapped.

Workaround

Workarounds include using either the orb (linked above) or the webhooks v2 - both with limited functionality.