1487172 - Stop generating bz2 balrog blob on non esr60 branches.

Status: RESOLVED FIXED

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

Description

[Tom Prince [:tomprince]]

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 1

[Tom Prince [:tomprince]]

Attachment: Bug 1487172: [release] Don't create -bz2 balrog blobs on non-esr60 branches; r?bhearsum

Comment 2

[[e-mail] (:bhearsum)]

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.

Comment 3

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/a9116d4316c7
[release] Don't create -bz2 balrog blobs on non-esr60 branches; r=bhearsum

Comment 4

[Bogdan Tara[:bogdan_tara | bogdant]]

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

Comment 5

[Nick Thomas [:nthomas] (UTC+12)]

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.

Comment 6

[Tom Prince [:tomprince]]

https://hg.mozilla.org/releases/mozilla-esr60/rev/43b68d042f4e