Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Artifacts not uploaded on Sentry on Vercel build #43007

Open
1 task done
ajouve opened this issue Nov 16, 2022 · 3 comments
Open
1 task done

Artifacts not uploaded on Sentry on Vercel build #43007

ajouve opened this issue Nov 16, 2022 · 3 comments
Labels
examples Issue was opened via the examples template. stale The issue has not seen recent activity.

Comments

@ajouve
Copy link

ajouve commented Nov 16, 2022

Verify canary release

  • I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
  Platform: darwin
  Arch: x64
  Version: Darwin Kernel Version 21.6.0: Mon Aug 22 20:17:10 PDT 2022; root:xnu-8020.140.49~2/RELEASE_X86_64
Binaries:
  Node: 16.14.0
  npm: 8.3.1
  Yarn: 1.22.15
  pnpm: 6.11.0
Relevant packages:
  next: 13.0.3
  eslint-config-next: 13.0.3
  react: 18.2.0
  react-dom: 18.2.0

What browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

Vercel

Describe the Bug

As I am using a private Gitlab server, this is the way I am deploying my app using Vercel

DEPLOYMENT_URL=$(VERCEL_ORG_ID=$VERCEL_ORG_ID VERCEL_PROJECT_ID=$VERCEL_PROJECT_ID vercel --yes --force \
    --token $VERCEL_TOKEN \
    --env NEXT_PUBLIC_SENTRY_DSN=$SENTRY_DNS \
    --build-env NEXT_PUBLIC_SENTRY_DSN=$SENTRY_DNS \
    --build-env SENTRY_AUTH_TOKEN=$SENTRY_AUTH_TOKEN \
    --build-env SENTRY_RELEASE=$CI_COMMIT_SHA \
    --env SENTRY_RELEASE=$CI_COMMIT_SHA \
    --regions fra1 )

vercel alias set $DEPLOYMENT_URL $APPLICATION_URL -t $VERCEL_TOKEN --scope ajouve

Expected Behavior

When I am running a npm run build in my local environment or in my gitlab-ci pipeline with the variables SENTRY_AUTH_TOKEN set I have my artifacts uploaded on sentry

I expect the artifacts to be uploaded with Vercel

See the attached screenshot, the 0 are the deploys from vercel and the 166 from local or gitlab ci

Screenshot 2022-11-16 at 19 04 47

Link to reproduction - Issues with a link to complete (but minimal) reproduction code will be addressed faster

https://github.com/vercel/next.js/tree/canary/examples/with-sentry

To Reproduce

Create app, add sentry deploy with vercel cli

@ajouve ajouve added the bug Issue was opened via the bug report template. label Nov 16, 2022
@balazsorban44 balazsorban44 added examples Issue was opened via the examples template. and removed bug Issue was opened via the bug report template. labels Nov 17, 2022
@lforst
Copy link
Contributor

lforst commented Dec 19, 2022

The SDK will currently only upload source artifacts in the production stage. Are you experiencing the same issue even when promoting builds to production?

@ajouve
Copy link
Author

ajouve commented Jan 3, 2023

I got a solution there https://stackoverflow.com/questions/74581114/artifacts-not-uploaded-on-sentry-on-vercel-build
because I am not using the prod system

@vercel-release-bot
Copy link
Collaborator

This issue has been automatically marked as stale due to two years of inactivity. It will be closed in 7 days unless there’s further input. If you believe this issue is still relevant, please leave a comment or provide updated details. Thank you.

@vercel-release-bot vercel-release-bot added the stale The issue has not seen recent activity. label Jan 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
examples Issue was opened via the examples template. stale The issue has not seen recent activity.
Projects
None yet
Development

No branches or pull requests

4 participants