How are Incident Investigations imagined to work with artifact releases vs Bitbucket repos?

Question

I love the potential of leveraging Bitbucket repos to aide in Incident root cause analysis but it currently assumes the latest commits relate to a given deployment. This doesn't work for teams which host multiple client environments, deployed from multiple versioned artifacts.

To follow the current approach, we'd need a way to take in the following information for a given deployment/environment Service:

* The Artifact Service (e.g. JFrog, Nexus Repository, Maven)
* The mapped artifact IDs  = name & version
* Artifact ID mapping to bitbucket repo release (e.g. branch or tagged release)

I realize things like this isn't easy and takes time. Does anyone have intermediate ideas that go to the spirit of this functionality?

Mark Campbell-Vincent_ghir58 · Accepted Answer

Hi @Adam Benfer -

Sounds like instead of seeing "Commits added" in the Opsgenie incident investigation, you would rather have "Artifact versions added", or at least something that correlates to that. Is that correct? I understand that this would help pinpoint the artifact releases that were potential causes to an incident rather than commits that don't necessarily relate to the release.

Although I can't think of any workaround that would work for this use case, I'd be happy to open up a feature request for this if you'd like.