Add Nightly build id to bug after patch lands
Categories
(bugzilla.mozilla.org :: General, enhancement)
Tracking
()
People
(Reporter: mozbugz, Unassigned)
Details
When a patch lands in mozilla-central, a bugzilla comment is added, which looks like:
https://hg.mozilla.org/mozilla-central/rev/11541de3ca98
Status: NEW → RESOLVED
Closed: 2020-07-09 07:54 AEST
status-firefox80: affected → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla80
I think it would be really helpful if that comment also contained the corresponding "build id" in Nightly. For example to tell users when some feature/fix will be available, to more easily correlate crash reports with patches, etc.
Since this comment is currently added as soon as the patch lands in central, I'm guessing we would only know the "last build id without this patch".
Alternatively, this comment could be delayed, or there could be a separate comment later on, in order to show the more useful "first build id with this patch".
Another non-BMO alternative would be a simple service that could link bug numbers and build ids; IIRC there might already be such things, but I can never remember how to find them in the rare times I need them! Having build ids directly in the relevant bug, and be searchable, would be most helpful.
Bonus: Add later comments when the same patch moves to a Beta build id, and then to a Release build id.
Those comments are made by pulsebot - https://github.com/glandium/pulsebot
Please file your request there.
Note hg.mozilla.org already contains this information - look for "first release with" "last release without" sections on the commit's url: https://hg.mozilla.org/mozilla-central/rev/11541de3ca98
|
Reporter | |
Comment 2•6 years ago
|
||
(In reply to :glob (Byron Jones) 🎈 from comment #1)
Those comments are made by pulsebot - https://github.com/glandium/pulsebot
Please file your request there.
Will do, thanks.
Note hg.mozilla.org already contains this information - look for "first release with" "last release without" sections on the commit's url: https://hg.mozilla.org/mozilla-central/rev/11541de3ca98
A-ha! That's the too-obvious thing I can never remember, only one click away. 😅
|
||
Comment 3•6 years ago
|
||
The central merge messages are not from pulsebot.
|
|
||
Comment 4•6 years ago
|
||
Also note that a nightly is only built after something is merged to central, so it's not possible to add the buildid information in the same message.
|
|
Reporter | |
Comment 5•6 years ago
|
||
Re-opening.
Note that my feature request implies that there could be a new Bugzilla searchable field in each bug, so it's not only about who/whatever generates the merge messages (if not BMO).
(In reply to Mike Hommey [:glandium] from comment #3)
The central merge messages are not from pulsebot.
Oops, sorry; looks like those are created by https://github.com/mozilla/bugherder/
Given comment 4 - the build-id isn't known at merge time, and that the information is already available elsewhere, I'm going to WONTFIX this request.
This doesn't address searching, but I'm not sure how useful that is as it's trivial to query a VCS using commit SHA ranges.
Description
•