You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm having non persisten errors during next.js builds due to connectivity problems that cause inherit http requests of releases new/finalize commands fail.
Since SENTRY_HTTP_MAX_RETRIES only aplies to file related commands I'm forced to retry the entire build process even if previous steps succeed.
Feature request
To improve performance and prevent retries at higher levels (such as ci/cd job) it would be great to either extend SENTRY_HTTP_MAX_RETRIES to all requests or support new segmented variables like SENTRY_HTTP_MAX_RETRIES_{KIND}
The text was updated successfully, but these errors were encountered:
Context:
I'm having non persisten errors during next.js builds due to connectivity problems that cause inherit http requests of
releases new/finalize
commands fail.Since
SENTRY_HTTP_MAX_RETRIES
only aplies to file related commands I'm forced to retry the entire build process even if previous steps succeed.Feature request
To improve performance and prevent retries at higher levels (such as ci/cd job) it would be great to either extend
SENTRY_HTTP_MAX_RETRIES
to all requests or support new segmented variables likeSENTRY_HTTP_MAX_RETRIES_{KIND}
The text was updated successfully, but these errors were encountered: