Sentry exceptions in release-tools need to include the CI_JOB_URL if available
We actually already do this, however I suspect that when the Sentry exception is coming from logger.fatal
, the SemanticLogger Sentry appender isn't including the default Raven-configured context.
Similarly, Elasticsearch log entries should include the runner host if possible, since Sentry does have that information, and we need to be able to correlate between the two when an exception occurs.