1645425 - Annotate Sentry reports with a "release version"

Status: RESOLVED FIXED

(Firefox Build System :: Mach Core, enhancement, P3)

Description

[Mitchell Hentges [:mhentges] 🦀]

As we resolve problems, developers working on an outdated checkout of the tree will be running into (and having issues reported) that are already fixed.

Sentry has a "release" feature which helps automatically filter "resolved" reports from old releases.

I'm thinking that we can capture the current mach """release""" by using the id of the most-recent public revision that is an ancestor of the checked-out revision.

Comment 1

[Mitchell Hentges [:mhentges] 🦀]

I'm thinking that we can capture the current mach """release""" by using the id of the most-recent public revision that is an ancestor of the checked-out revision.

This might be tricky to do with git-cinnabar, I'm not sure that it track the "most-recent central revision in the current set of ancestors" quite like hg can.
I'll investigate this.

Comment 2

[Mitchell Hentges [:mhentges] 🦀]

Attachment: Bug 1645425: Annotate Sentry reports with base revision

To track whether issues being reported are for old versions, we attach
an hg revision hash as a release version with each report.

We use the base_ref because:

• It's a public revision that we can look up, and
• Since we only submit Sentry events when mach is unmodified,
  it's essentially acting as a version identifier.

Comment 3

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/eed530931ca0
Annotate Sentry reports with base revision r=sheehan

Comment 4

[Dorel Luca [:dluca]]

https://hg.mozilla.org/mozilla-central/rev/eed530931ca0