Open RobinDaugherty opened 7 years ago
To amplify, here is what I have observed:
ENV.APP.version
when sending an exception report to sentry.ENV.APP.version
generated? No idea yet, will require a lot of reading of code. It is however, package version + git commit.ENV.APP.version
during deployment? Doesn't seem possible to get access to the build information in environment.js
.I tried adding to my raven service:
import Raven from 'ember-cli-sentry/services/raven';
let releaseMetaTag = document && document.querySelector("meta[name='sentry:revision']");
let release = releaseMetaTag && releaseMetaTag.getAttribute('content');
if (release) {
Raven.callRaven('setRelease', release);
}
export default Raven.extend({}) // snipped the boilerplate
This fails. Should I instead use window.Raven
directly? Is this even the correct place to do this?
I originally worked on this... it doesn't work as well as it should. The break (as you note correctly) is in that ENV.APP.version
is used for sending an exception report, which was supposed to be meta[name='sentry:revision']
but has deviated from it, in a way that I don't recall.
This already was supposed to be happening (see https://github.com/dschmidt/ember-cli-deploy-sentry/commit/2a561ff19d19afab5eae338c47707f9c8729c8a8) but something, somewhere went wrong...
Your Raven service sounds good - quite possibly we should stick something like that in an initializer instead of a service.
The readme says:
How is this supposed to work with ember-cli-sentry?