Skip to content

Help with Sentry release id not matching Ember deploy S3 revision id #65

Open
@danr1979

Description

@danr1979

Hi.

I deploy my Ember app to S3 using https://github.com/ember-cli-deploy/ember-cli-deploy-s3, which gives me a revision id for each deployment to production. In the attached screenshot you can see that on Sentry my revision id (the longer id) does not match the release id that Sentry is receiving errors on. Therefore, my source maps are not being matched correctly and I can't see my code to debug it correctly in Sentry.

In the guide I read the following tip that seems to suggest that ember-cli-deploy-sentry will handle the matching for me but this is not working for me (how would ember-cli-deploy-sentry know what revision id ember-cli-deploy-s3 is using?)

Install ember-cli-sentry but import the raven service from ember-cli-deploy-sentry/services/raven, which will automatically handle setting up the release version for you.

I'm sorry if this is a dumb question but how do I ensure that my s3 deploy revision id matches my sentry release id? Is there some way I can manually configure the behaviour I need?

Any help would be appreciated.

Thanks.

Releases - acceptacard-ltd - Sentry

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions