Link to GitLab commit on the Sentry error detail page

Problem to solve

With Continuous Delivery, a common way to name a Sentry Releases is with the SHA of the deployed commit. By following this standard, it is now possible to directly relate a Sentry error to a GitLab commit in GitLab. If we defined this as the expected process, we could use the Sentry Release name as our "suspect commit".

Linking a Sentry error directly to the commit that very recently generated the error gives the user the ability to immediately roll-back the change or fix the specific place in code causing the error and deploy a patch.

Intended users

• Delaney (Development Team Lead)
• Sasha (Software Developer)
• Devon (DevOps Engineer)
• Sidney (Systems Administrator)

Further details

This work supports the Error Tracking Vision.

Proposal

Parse the name of the Sentry release passed via the API to GitLab. Check to see if it matches any commit SHAs for the repo. If it matches, surface and link the GitLab commit in the error detail page. If it does not match any commits, do not show anything.

Proposed design

Permissions and Security

Documentation

Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Links / references

Original Spike #36252 (closed)