This patch adds support for Workers to emit various RSpecQ internal events to
a Sentry[1] instance.
Reporting to Sentry is opt-in and is enabled by setting the SENTRY_DSN
environment variable (see
https://github.com/getsentry/raven-ruby#raven-only-runs-when-sentry_dsn-is-set).
If SENTRY_DSN is not set this is a noop.
Events emitted:
- [error] the spec file split command failed; slow spec files files will
be scheduled as a whole so build times will be negatively impacted
- [warning] no previous timings were found in Redis; scheduling will be random
so build times will be negatively impacted
- [info] slow files were detected and will be split, including the
actual filenames
The above are still printed to the standard output of the worker.
Closes#8
[1] https://sentry.io
Cody Cutrer