Automatically report deployed releases to integrated Sentry server
Problem to solve
Reporting releases to Sentry today is a manual process. Sentry requires notification of what commits a release contains, and when it is deployed, in order for their tracking logic to work.
We can potentially automate this with our integration, since we in theory know when something is being deployed to a given environment and for what branch/tag/ref.
This could significantly reduce the effort required to get this integration working, and see the benefits in determining impact of releases as well as suspicious commits.
- Delaney (Development Team Lead)
- Sasha (Software Developer)
- Devon (DevOps Engineer)
- Sidney (Systems Administrator)
This work supports the Error Tracking Vision.
Our internal Delivery team built scripts for this purpose. I do not believe that they are creating releases and reporting associated commits ahead of releases. We may be able to re-use the scripts they have built and offer it for customers.
Permissions and Security
Documentation required, most likely here.
What does success look like, and how can we measure that?
What is the type of buyer?
Links / references