[Question] How to disable sentry releases on `next build` in CI mode?

[kachar]

On every PR in our codebase we run next build in CI to verify that the build process is not affected by the PR.

We're recently upgraded to the new @sentry/nextjs package and wonder how to disable releasing the temporary CI builds to Sentry.

We've also had hard time running the build in CI mode as we had to provide SENTRY_AUTH_TOKEN for the build to succeed.

At the moment I don't see clear procedure of disabling the releases, please guide me if such exists.

(Adding it as issue as discussions are not enabled for this repo)

[iker-barriocanal]

The second parameter of withSentryConfig is the Webpack Plugin options. You can set dryRun to true, and it shouldn't be uploading source maps to Sentry.

So your next.config.js should look something like this:

const { withSentryConfig } = require('@sentry/nextjs');

const moduleExports = {};

const SentryWebpackPluginOptions = {
  dryRun: process.env.CI
};

module.exports = withSentryConfig(moduleExports, SentryWebpackPluginOptions);

Let me know if this works for you.

[kachar]

@iker-barriocanal Yep! The option dryRun works nicely 🙌 Thanks for the update

I've used the application environment as well as the CI

The default for github actions seems to be CI / process.env.CI docs but it is not passed to the build straight away as we're using .env file

Instead of that I'm checking against the application environment we're building for

const { withSentryConfig } = require('@sentry/nextjs');

const moduleExports = {};

const SentryWebpackPluginOptions = {
  debug: ['staging', 'production'].includes(process.env.APP_ENV) || false,
  dryRun: ['development', 'nightly'].includes(process.env.APP_ENV) || true,
}

module.exports = withSentryConfig(moduleExports, SentryWebpackPluginOptions)

https://github.com/daritelska-platforma/frontend/blob/0d12a0d5dd0997bac133925b50acb5e134c83a18/frontend/next.config.js#L43-L45

[iker-barriocanal]

Awesome!

[kachar]

However even if dryRun mode is set, Sentry release procedure is being prepared, which takes time and now next build is taking twice the time of regular build.

[lobsterkatie]

Hi, @kachar. Sorry, missed this in my initial sweep when I merged the PR. You can now disable this behavior. Docs are here.