3 ms·
No, it cant. Read the damn file you linked. It’s a script that uploads release files to Sentry so it can be used while correlating crash reports, when a release
by orf 5y ago
No, it cant. Read the damn file you linked. It’s a script that uploads release files to Sentry so it can be used while correlating crash reports, when a release is made.
And nobody in their right mind would ever send crash reports to Sentry from a CI. That’s completely nonsensical.
- ljm 5y agoIt would be an expensive way to report on a test suite, I'll give you that.
- viraptor 5y agoIt depends on what you're trying to achieve. It's totally reasonable to report stack traces from the CI, especially from the master branch for a quick overview on flakey tests. I don't know anything about their setup specifically, but that approach does have use cases.
- orf 5y agoIt’s not “totally reasonable” to send CI stack traces to Sentry. It’s nonsensical for a number of reasons.
- viraptor 5y agoFor me it solves the issue of tracking flakey tests. It's the easiest way to do it if you're already using the same error reporting platform in production. Please consider others' use cases before declaring this nonsensical.
- untitaker_ 5y agoviraptor was not really responding to the discussion about the shell script at all (which is weird in its own right), but was rather talking about stuff like https://github.com/getsentry/pytest-sentry https://github.com/getsentry/pytest-sentry