-
Notifications
You must be signed in to change notification settings - Fork 111
Closed
Labels
Description
Version
@nuxtjs/sentry: 7.3.0
nuxt: 2.15.8
@sentry/webpack-plugin: 1.20.1
Sentry configuration
sentry: {
dsn: KEY,
disabled: isLocal,
publishRelease: {
authToken: process.env.SENTRY_AUTH_TOKEN,
org: process.env.SENTRY_ORG,
project: process.env.SENTRY_PROJECT,
setCommits: {
auto: true,
ignoreMissing: true
},
ignore: [
'node_modules',
'.nuxt/dist/client/img'
],
},
logMockCalls: false,
sourceMapStyle: 'hidden-source-map',
config: {
environment: process.env.APP_ENV,
release: process.env.GIT_COMMIT_SHA,
captureUnhandledRejections: false,
},
clientConfig: {
attachProps: true,
trackComponents: true,
},
},
Steps to reproduce
I build project on the one commit hash twice (one on stage server and one on prod).
What is Expected?
Second build should be successful too
What is actually happening?
First build is successful, second catches build error:
ERROR in Sentry CLI Plugin: Command failed: ../node_modules/@sentry/cli/sentry-cli releases set-commits {hash} --auto --ignore-missing
error: No commits found. Change commits range, initial depth or use --ignore-empty to allow empty patch sets.
Reactions are currently unavailable