Unable to see suspect commits

Integrations
1

Hey there!.

I’ve connected my GitHub account to Sentry in order to get the “Suspect commits” feature working.

I’m creating releases with commits in the Sentry CLI tool and I can see them in the Releases section of the Sentry dashboard.

      sentry-cli releases new -p $SENTRY_PROJECT $SENTRY_RELEASE
      sentry-cli releases set-commits --auto $SENTRY_RELEASE
      sentry-cli releases finalize $SENTRY_RELEASE
      sentry-cli releases deploys $SENTRY_RELEASE new -e $ENV

I’ve created a sample error and it gets reported under Issues, but I don’t see the Suspect Commit UI?

Am I missing something or should this populate automatically after setting up the integration and releasing the version in Sentry?

2

You’re not alone as there have been a couple other forum posts describing the same issue:

I’ve since reached out to support to see if they have any ideas.

3

Hey Bryan, thanks for replying. Hoping the Sentry team answers.

I see. Have you tried setting up releases with CLI, API or both?

4

Do you need to connect artifacts to a release in order for Suspect Commit to work?. I’m reading a guide on https://docs.sentry.io/guides/integrate-frontend/upload-source-maps/ and they are associating the artifacts.

But I’m using normal CRA and the Issues’s stack trace looks correct without publishing artifacts.

5

Using both currently.

I’m not sure. Uploading artifacts has worked as far as revealing the issue in the stack trace.

6

Hi @jamzi - is this on sentry.io or on-premise?

7

I encountered the same issue on sentry.io. The Github repository is connected, the release contains commits and changed files information, the issues are attached to releases automatically, but suspect commits and assignee are never appearing in the issues.

8

I run into the same problem using the API. The official documentation is a little vague here. In one examples from Sentry documentation version is set to git commit hash in another to two digit version number. The example also states: it is assumed: source maps are uploaded, which I cannot do as I’m testing it with a simple python project. Source maps cannot be a requirement for suspected commits to work, or can it be? Finalizing realease thorugh API is not documented: I guess by setting th dateReleased… What happens when I deploy “unfinalized” release, will it be finalized automatically?