How do I configure and troubleshoot Sentry CLI for release creation?
Sentry CLI is a powerful tool that can help with managing releases and source maps in Sentry. Proper configuration and troubleshooting are essential for ensuring smooth operations. Below are key steps to configure and debug Sentry CLI effectively.
Enabling Debug Logs for Sentry CLI
To diagnose issues with Sentry CLI commands, you can enable full debug logs. This provides detailed output that can help identify problems during execution. Use the --log-level=DEBUG flag with your Sentry CLI command. For example:
npx @sentry/cli sourcemaps upload --log-level=DEBUG ...
This command will produce comprehensive logs, making it easier to troubleshoot issues during release creation or source map uploads.
Alternatively, you can set the environment variable like this:
export SENTRY_LOG_LEVEL=debug
Configuring the Correct Sentry URL
When using Sentry CLI, it is crucial to set the correct Sentry URL based on your organization's hosting region. Follow these guidelines:
For US-hosted organizations, use the standard Sentry URL: https://sentry.io (default, no need to set)
For EU-hosted organizations, use the EU-specific Sentry URL: https://de.sentry.io
If using a personal auth token, set SENTRY_URL to your region's base URL (e.g. https://de.sentry.io for EU). If using an organization auth token, the URL is embedded in the token and does not need to be configured separately. In either case, ensure your token is valid and not revoked to avoid 401 errors.