Closed Bug 1462064 Opened 3 years ago Closed 3 years ago

sha1 is esr52 only so release bouncer check on esr60 should stop checking it


(Release Engineering :: Release Automation: Other, enhancement)

Not set


(firefox63 fixed)

Tracking Status
firefox63 --- fixed


(Reporter: mtabara, Assigned: mtabara)



(Whiteboard: [releaseduty])


(1 file)

No description provided.
Assignee: nobody → mtabara
Likely we need to strip these from mozharness configs for esr or so.
I agree, we need to split this mozharness config[1]:

> ./mach python testing/mozharness/scripts/release/ --version=60.0.2esr --previous-version=60.0esr --previous-version=60.0.1esr --config releases/

In other news, firefox-sha1-ssl points to 52.7.3esr-sha1 while firefox-sha1 points to Firefox-52.9.0esr-sha1.
We might need to update the esr52 configs to update that firefox-sha1-ssl alias as well.
See Also: → 1471223
esr52 releases uptake monitoring jobs are green and happy but the esr60 counterpart fail for 404s when it comes to the same files.

I was going to originally split the bouncer_firefox_esr and tweak it accordingly in bbconfigs + tree but then I realized things could be even more simplified.

We let esr52 do its own things. It's going to die anyway soon along with all bbconfigs and such.

In the meantime, we remove sha1 once and for all and we land this to central/beta/release/esr60 to make sure when we'll branch off esr67 we won't hit this again.

How's this sound?
Attachment #8991485 - Flags: review?(rail)
Attachment #8991485 - Flags: feedback?(nthomas)
Comment on attachment 8991485 [details] [diff] [review]
Remove sha1 installer from esr60 ongoing

Review of attachment 8991485 [details] [diff] [review]:

Attachment #8991485 - Flags: feedback?(nthomas) → feedback+
Attachment #8991485 - Flags: review?(rail) → review+
Pushed by
prevent release-bouncer-check test against sha1 installers. r=rail a=release
I'll let Sheriffs close this bug by merging this to central.
Closed: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.