Closed Bug 1698511 Opened 3 years ago Closed 3 years ago

On mozilla-central, inform Sentry of new revisions

Categories

(Firefox Build System :: Task Configuration, task)

task

Tracking

(firefox89 fixed)

RESOLVED FIXED
89 Branch
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: nobody → mhentges
Status: NEW → ASSIGNED
Blocks: 1645425
See Also: → 1698815
Depends on: 1698815
See Also: 1698815

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.

mozilla-central jobs need to have access to the private
Sentry API key in order to use the sentry-cli.

Attachment #9211380 - Attachment description: WIP: Bug 1698511: Publish revisions as mach releases in Sentry → Bug 1698511: Publish revisions as mach releases in Sentry
Attachment #9211382 - Attachment description: WIP: Bug 1698511: Add Sentry secret scope to `mozilla-central` → Bug 1698511: Add Sentry secret scope to `mozilla-central`
Pushed by asasaki@mozilla.com:
https://hg.mozilla.org/ci/ci-configuration/rev/09f982617f8e
Add Sentry secret scope to `mozilla-central` r=aki
Pushed by mhentges@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/9d85f4ffd546
Publish revisions as mach releases in Sentry r=aki
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 89 Branch

Temporarily allow access to garbage/mhentges for testing
task<->secret integration.

Attachment #9211779 - Attachment description: WIP: Bug 1698511: Allow access to a garbage secret in try for testing → Bug 1698511: Allow access to a garbage secret in try for testing
Pushed by bhearsum@mozilla.com:
https://hg.mozilla.org/ci/ci-configuration/rev/1a8cad8e15d9
Allow access to a garbage secret in try for testing r=bhearsum

Now that the cause of the Sentry-release-publishing issue
has been resolved, we can remove the temporary testing
permissions.

Attachment #9211799 - Attachment description: WIP: Bug 1698511: Remove access to garbage testing secret → Bug 1698511: Remove access to garbage testing secret
Pushed by bhearsum@mozilla.com:
https://hg.mozilla.org/ci/ci-configuration/rev/77bfd86a67ad
Remove access to garbage testing secret r=bhearsum

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.

Attachment #9212334 - Attachment is obsolete: true
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: