Workflow 2.0 - Improving release monitoring with commit metadata

[NisanthanNanthakumar]

A key objective of Workflow 2.0 is improving the quality of release notifications, which relies heavily on accurately associating releases with code commits and the users associated with these commits. With this information, we can provide timely and actionable notifications to users who are most invested in a release.

We aim to give users the ability to share commit metadata in one of two ways:

1. Using Sentry CLI to create releases during your application build pipeline. Run the CLI commands in your CI to automatically complete Sentry’s release workflow everytime you deploy.
2. Leveraging Sentry’s integrations with popular source code management tools like GitHub, GitLab, BitBucket, and Azure Devops. If you don’t use the CLI, Sentry can create a release when the SDK generates an event with a new release version. If the version corresponds to the SHA of the head commit at deployment, Sentry will automatically determine which commits are associated with this release using the source code integrations. We are working on this capability and will be deploying this in the near future.

We just deployed a quickstart for releases here, that you'll see if you have not yet set up a release for the selected project. Here, you'll be able to copy and paste the code snippet directly into your CI config file.

We will be iterating upon this page to reduce friction.

We are also enhancing our GitHub integration to make it easier to use and will be rolling out improvements over the coming weeks.

Developers will have the flexibility to choose the approach that works best for them. We’re about developers first!

Do share your thoughts on these approaches and how else we could make gathering commit metadata more effective.