Have Sentry fail gracefully during build phase

[lukemun]

Problem Statement

Sentry integration with popular build plugins can fail while uploading sourcemaps.

[08:16:55.637] unhandledRejection [Error: Command failed: /vercel/path0/node_modules/@sentry/cli-linux-x64/bin/sentry-cli releases new...
[08:16:55.637] error: API request failed
[08:16:55.637]
[08:16:55.638] Caused by:
[08:16:55.638]     sentry reported an error: unknown error (http status: 503)

This will fail the entire build process and potentially block deployments.

Is there a wail to fail gracefully to not block CI but still alert the user?

Solution Brainstorm

No response

Product Area

Issues - Source Maps

[getsantry]

Auto-routing to @getsentry/product-owners-issues for triage ⏲️

[lobsterkatie]

Transferring this to the JS SDK repo, as that's what mediates this process.

[MaxwellCohen]

I had a build failure because of this issue yesterday morning. here is the part of the logs that are the result of the issue

 Running "npm run build"
 
 > web-perf-reporting@0.1.0 build
 > next build
 
    ▲ Next.js 15.1.7
    - Experiments (use with caution):
      · clientTraceMetadata
 
    Creating an optimized production build ...
 [@sentry/nextjs - Node.js] Info: Sending telemetry data on issues and performance to Sentry. To disable telemetry, set `options.telemetry` to `false`.
 unhandledRejection [Error: Command failed: /vercel/path0/node_modules/@sentry/cli-linux-x64/bin/sentry-cli releases new 49d7d4373d3d50eba3f357e5c23098ba99130093
 error: API request failed
 
 Caused by:
     sentry reported an error: unknown error (http status: 503)
 
 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.
 ] {
   code: 1,
   killed: false,
   signal: null,
   cmd: '/vercel/path0/node_modules/@sentry/cli-linux-x64/bin/sentry-cli releases new 49d7d4373d3d50eba3f357e5c23098ba99130093'
 }
Error: Command "npm run build" exited with 1

[Lms24]

Transferred the issue to our bundler plugins repo which is where we need to make changes.

These crashes likely propagate from Sentry CLI exiting with an error: getsentry/sentry-cli#1242

We'll take a look at handling this and degrading better in the plugins.