On mozilla-central, inform Sentry of new revisions
Categories
(Firefox Build System :: Task Configuration, task)
Tracking
(firefox89 fixed)
Tracking | Status | |
---|---|---|
firefox89 | --- | fixed |
People
(Reporter: mhentges, Assigned: mhentges)
References
Details
Attachments
(4 files, 1 obsolete file)
In 1645425, we send each Sentry report with the public revision it's based off of.
However, Sentry doesn't know the order of revisions, so using features like "this report is fixed in <next release>" don't work.
Whenever code lands in mozilla-central
, we should inform Sentry of all the revisions that are now "released".
Note that this task will need access to a private Sentry token.
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Comment 1•4 years ago
|
||
To identify regressions and existing exceptions in Sentry, we tag them
with their mach release (the current base revision).
To ensure that Sentry knows the correct order of revisions, we need to
tell it about each one that lands in mozilla-central.
Assignee | ||
Comment 2•4 years ago
|
||
mozilla-central
jobs need to have access to the private
Sentry API key in order to use the sentry-cli
.
Updated•4 years ago
|
Updated•4 years ago
|
Comment 5•4 years ago
|
||
bugherder |
Assignee | ||
Comment 6•4 years ago
|
||
Temporarily allow access to garbage/mhentges
for testing
task<->secret integration.
Updated•4 years ago
|
Assignee | ||
Comment 8•4 years ago
|
||
Now that the cause of the Sentry-release-publishing issue
has been resolved, we can remove the temporary testing
permissions.
Updated•4 years ago
|
Comment 10•4 years ago
|
||
Comment 11•4 years ago
|
||
Comment on attachment 9212334 [details]
Bug 1698511 - grant engworkflow team access to engwf secrets r=#releng-reviewers
Revision D110163 was moved to bug 1701359. Setting attachment 9212334 [details] to obsolete.
Description
•