search

getsentry / sentry

Developer-first error tracking and performance monitoring
https://sentry.io
Other
38.91k stars 4.17k forks source link

Monorepo with two projects, source Maps uploading two different keys. Github onBuild actions accept a single key. #71905

Closed lveillard closed 4 months ago

lveillard commented 4 months ago

Environment

SaaS (https://sentry.io/)

What are you trying to accomplish?

We have a monorepo with two nextjs apps.

We installed sentry in both apps, and asigned them to two different projects.

We just want the sourcemap to be uploaded during build time, all apps are build at once, or individually depending on the needs

How are you getting stuck?

We want to split each app in a single project, but then we get 2 different auth keys for the sourcemap upload.

The problem is that in the github actions we can set up a single one, so we should unify the sourcemap upload, while having two different projects in the same monorepo.

ORG ID: blitz-no-code

Where in the product are you?

Issues - Source Maps

Link

No response

DSN

No response

Version

No response

getsantry[bot] commented 4 months ago

Assigning to @getsentry/support for routing ⏲️

getsantry[bot] commented 4 months ago

Routing to @getsentry/product-owners-issues-source-maps for triage ⏲️

lforst commented 4 months ago

Hi, you can absolutely just use the same key for both of the projects when uploading.

lveillard commented 4 months ago

Oh perfect. Thanks! For UX I guess it would make sense to don't generate one key on every setup for the same account, similar as how highligh.io does it

Also the auto patcher is really cool, but it does not check if the code is already there, so if you run it twice to change some configs, it actually duplicates most of the code (at least for the nextjs one)

Closing this, will reopen if i find any issue by using the same key for different projects.

Thanks!