Skip to content

Should fail gracefully if SHA of the previous release commit wasn't found #10

Closed
getsentry/sentry-cli
#963
@rreckonerr

Description

@rreckonerr

While moving from ember-cli-deploy-sentry to your addon I've noticed that if sentry-cli is unable to find the previous release commit SHA it'll throw an error and break the build pipeline.

We're deploying from release branches and SHA will be lost after the branch is rebased, so it'd be nice if there was a workaround for that. Do you have any ideas?

Log

Error: Command failed: node_modules/.bin/sentry-cli  --auth-token XXX releases --org XXX --project XXX set-commits --auto XXX@XXX+XXX
error: Could not find the SHA of the previous release in the git history. Increase your git clone depth.

Add --log-level=[info|debug] or export SENTRY_LOG_LEVEL=[info|debug] to see more output.
Please attach the full debug log to all bug reports.

Steps to reproduce

  1. Add a fixup commit
  2. Deploy
  3. Squash
  4. Deploy

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions