Closed Bug 1413688 Opened 7 years ago Closed 7 years ago

releng war room and rehearsal prep - determine infra vectors that affect pushing a release live

Categories

(Release Engineering :: Release Requests, defect)

Product:
Release Engineering
Component:
Release Requests
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: jlund, Unassigned)

References

Details

As part of FF Quantum release, releng will be coordinating with various teams in a rehearsal on Nov 9th and join the War Room on Nov 14th, release day. More details on both of those to come but in the mean time, we should determine the following: how long does it take for a release to "go live" on mozilla.org from the point that relman request to do so? What risks (factors) affect that? This is good practice to know more generatlly so there are benefits outside of this special release case. I've split the work in this bug by tasks involved within a release graph and work that happens after. In other words: 1) releng taskcluster release graph a) What tasks are triggered by this[0] and how long do they take to complete? b) factors that affect overall duration: Taskcluster worker availability. Buildbot pending. BBB health. 2) Mozilla.org availability a) how long after (1) completes does it take for mozilla.org to show the release as available? b) factors that affect overall duration: bouncer efficiency, caching logic, etc [0] https://github.com/mozilla/releasewarrior/blob/master/how-tos/relpro.md#how-3
Somehow offtopic: bug 937865 just got fixed. 57.0 might be our first release to avoid the "unknown ~´20-25mins propagation from Ship-it to mozilla.org via bedrock". Once they update the entries in the webiste, from versions to latest bouncer updates, we should have the release available as soon as bouncer aliases task runs. I asked a question there in the bug to see if this is going to happen but it's something to take into account as a heads-up at least, if they add it! \o/
Thanks Mihai. Completely relevant and useful. Nick and I met and he has a lot of great ideas. I've started a doc / checklist for Tues: https://gist.github.com/lundjordan/3b2f5ba3455fbfe2f8e7a8fcb6c85dfb
57 shipped. all done here.
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.