next.js icon indicating copy to clipboard operation
next.js copied to clipboard

Artifacts not uploaded on Sentry on Vercel build

Open ajouve opened this issue 3 years ago • 0 comments

Verify canary release

  • [X] 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 avatar Nov 16 '22 18:11 ajouve