Open jinsley8 opened 1 year ago
Routing to @getsentry/ecosystem for triage. ⏲️
This doesn't look like an issue with our Vercel integration. Rather this looks related to our webpack plugin https://github.com/getsentry/sentry-webpack-plugin or the underlying sentry-cli
Routing to @getsentry/sdks
This doesn't look like an issue with our Vercel integration. Rather this looks related to our webpack plugin https://github.com/getsentry/sentry-webpack-plugin or the underlying sentry-cli
Routing to @getsentry/sdks
Should I repost this under the Sentry webpack repo?
Sorry, bot fail. 😞
Hi, what I recommend doing here, and I do this in my side project too, is the following:
setCommits: {
repo: 'lforst/my-repo',
commit: process.env.VERCEL_GIT_COMMIT_SHA,
previousCommit: process.env.VERCEL_GIT_PREVIOUS_SHA,
},
Note that auto
can't be set. I think it fails because on Vercel the project is not inside a git repo anymore. We should maybe emit better error messages here and fail gracefully instead.
Idea on how to fix this: We try-catch the setCommits
command and log a warning/error with instructions on how to fix this. Actually.... Not sure yet if we should keep throwing or not. Throwing will definitely be more visible when you set up the plugin so we should maybe do that.
Environment
SaaS (https://sentry.io/)
Version
No response
Steps to Reproduce
I have Sentry connected to Vercel and GIthub and the following next.config.js:
However, the Vercel build fails at the Sentry CLI step.
Expected Result
Expect to Vercel build to pass and to deploy.
Actual Result
Not sure if it's failing because my config is incorrect or because Next.js using SWC as a default now instead of Webpack.
┆Issue is synchronized with this Jira Epic by Unito