Closed Bug 1382043 Opened 7 years ago Closed 7 years ago

Freeze nightlies for m-c on first 20170718 nightly

Categories

(Release Engineering :: General, enhancement, P1)

Product:
Release Engineering
Component:
General
Type:
enhancement

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: nthomas, Assigned: nthomas)

References

Details

Bug 1382019 has made nightly crash, lets disable updates and figure out the last good until we have a good nightly again.
Mapped rule id 3 to No-Update to disable updates.
Based on the 'first release with' data at https://hg.mozilla.org/mozilla-central/rev/5e73b9798464c3f7106f0161dc9a49b234f42f9c I pulled Firefox-mozilla-central-nightly-{20170718030207,20170718100239,20170718100333} releases from Balrog, and merged them into
Firefox-mozilla-central-nightly-20170718030207+20170718100239+20170718100333. Uploaded that to Balrog and pointed rule id 3 at it.

When we have the all clear we can point back to Firefox-mozilla-central-nightly-latest.
Priority: -- → P1
Summary: Disable nightlies for m-c → Freeze nightlies for m-c on first 20170718 nightly
Posted notifications to dev.platform and release-drivers. 

Sheriff's, please advise when we should unfreeze again.
As a quick update here - we're still waiting on Windows l10n repacks to finish up for today's nightlies before giving the go-ahead. Everything else is finished.
Flags: needinfo?(wkocher)
Looks like everything's done now. We should be OK to unfreeze nightlies now.
(In reply to Ryan VanderMeulen [:RyanVM] from comment #5)
> Looks like everything's done now. We should be OK to unfreeze nightlies now.

I unfroze the nightlies by setting rule id 3 back to Firefox-mozilla-central-nightly-latest.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.