-
Notifications
You must be signed in to change notification settings - Fork 987
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Setup Sentry secrets on CI #21706
Comments
Depends on: So for now it's on hold. |
@jakubgs @markoburcul the implementation in PR #21682 should work because I tested it locally pointing to a cloud Sentry instance. So we can proceed with this issue. In The value for Once this issue #21706 is resolved I will proceed to rebase @igor-sirotin in status-desktop it appears that |
I don't see that file, do you want to create it or? Since in status-desktop as I can see those two env variables are passed in the Makefile. |
Thanks @markoburcul. The file is in this status-mobile repo at |
could you give me a link to this file on Github? |
@markoburcul it's this file
|
@ilmotta indeed, yes. I didn't bother with other environments for now, because we don't yet report to sentry from e2e tests.
❤ |
referenced issue: #21706 Signed-off-by: markoburcul <[email protected]>
referenced issue: #21706 Signed-off-by: markoburcul <[email protected]>
referenced issue: #21706 Signed-off-by: markoburcul <[email protected]>
referenced issue: #21706 Signed-off-by: markoburcul <[email protected]>
referenced issue: #21706 Signed-off-by: markoburcul <[email protected]>
referenced issue: #21706 Signed-off-by: markoburcul <[email protected]>
referenced issue: #21706 Signed-off-by: markoburcul <[email protected]>
referenced issue: #21706 Signed-off-by: markoburcul <[email protected]>
referenced issue: #21706 Signed-off-by: markoburcul <[email protected]>
referenced issue: #21706 Signed-off-by: markoburcul <[email protected]>
referenced issue: #21706 Signed-off-by: markoburcul <[email protected]>
referenced issue: #21706 Signed-off-by: markoburcul <[email protected]>
referenced issue: #21706 Signed-off-by: markoburcul <[email protected]>
referenced issue: #21706 Signed-off-by: markoburcul <[email protected]>
referenced issue: #21706 Signed-off-by: markoburcul <[email protected]>
referenced issue: #21706 Signed-off-by: markoburcul <[email protected]>
referenced issue: #21706 Signed-off-by: markoburcul <[email protected]>
referenced issue: #21706 Signed-off-by: markoburcul <[email protected]>
referenced issue: #21706 Signed-off-by: markoburcul <[email protected]>
Sentry integration is done here: status-im/status-go#6054
Description
We want to keep Sentry DSN private, so we need to provide some environment variables on CI.
The following env vars need to be defined on PRODUCTION CI only.
Not for PR-level or develop builds.
SENTRY_DSN_STATUS_GO
to the DSN from hereSENTRY_PRODUCTION
totrue
The text was updated successfully, but these errors were encountered: