Closed Bug 1487172 Opened Last year Closed 11 months ago

Stop generating bz2 balrog blob on non esr60 branches.

Categories

(Release Engineering :: Release Automation: Updates, defect)

defect
Not set

Tracking

(firefox-esr60 fixed, firefox64 fixed)

RESOLVED FIXED
Tracking Status
firefox-esr60 --- fixed
firefox64 --- fixed

People

(Reporter: tomprince, Assigned: tomprince)

References

Details

Attachments

(1 file)

In Bug 1481121, for expediency, the tasks that create and schedule the bz2 balrog  weren't limited to run on mozilla-esr60. They don't change any rules, so the created blob is unreferenced, but could cause confusion.
Comment on attachment 9008821 [details]
Bug 1487172: [release] Don't create -bz2 balrog blobs on non-esr60 branches; r?bhearsum

Ben Hearsum (:bhearsum) has approved the revision.
Attachment #9008821 - Flags: review+
Pushed by mozilla@hocat.ca:
https://hg.mozilla.org/integration/autoland/rev/a9116d4316c7
[release] Don't create -bz2 balrog blobs on non-esr60 branches; r=bhearsum
https://hg.mozilla.org/mozilla-central/rev/a9116d4316c7
Status: NEW → RESOLVED
Closed: 11 months ago
Resolution: --- → FIXED
Assignee: nobody → mozilla
We're getting stub releases in Balrog for Firefox betas (eg Firefox-63.0b8-build1-bz2) because of not uplifting this fix to 63. Since the change here relies on other patches so we'll not uplift at this point in the beta cycle. I've removed the stray Firefox-63.0b*-build*-bz2 blobs, but expect we'll get a few more betas and all the 63.0 on release. We can remove those later.
You need to log in before you can comment on or make changes to this bug.