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
While many dev ecosystems are used to pull a binary and run via the CLI. In others, build system automation abstracts these. We integrate with many, such as Gradle, Fastlane and Webpack.
In the current integrations we have a mock server that simulates Sentry and validates things. This helps us integration test things such as symbol upload.
Hey @bruno-garcia, I was seeing some weird Sentry related errors during my build and I was a bit surprised to see that all this was added to the main Sentry package.
The errors I'm seeing are:
E:\.nuget\packages\sentry\3.28.1\buildTransitive\Sentry.targets(88,5): error : Sentry API request failed. Either the authentication info is invalid, or the Sentry server could not be reached.
Please note that I didn't opt-in to upload any info at all as I would need security team to approve it.
It's a geat feature but I feel like it should be added to another package like Sentry.MsBuild.
EDIT : I just saw #2216, I'll update to newest version it should fix my issue
Sentry CLI offers many features.
The main features we use during build phase of projects are:
While many dev ecosystems are used to pull a binary and run via the CLI. In others, build system automation abstracts these. We integrate with many, such as Gradle, Fastlane and Webpack.
In the current integrations we have a mock server that simulates Sentry and validates things. This helps us integration test things such as symbol upload.
Goals
sentry-cli
in the finalSentry
NuGet package - Use Sentry CLI after build to upload symbols #2107GitHub workflow to automatically open PR with updates for Sentry CLIUpload Release info to SentrySENTRY_ALLOW_FAILURE
env var<SentryUploadSymbols>true</SentryUploadSymbols>
in app csproj)Opt-in to upload commit infoRelates to:
enable-suspect-commits
team-mobile#33The text was updated successfully, but these errors were encountered: