optimize the priorities in the snowman model so that we make the graph more efficient
Categories
(Release Engineering :: General, enhancement)
Tracking
(firefox-esr60 wontfix, firefox-esr68 fixed, firefox69 fixed, firefox70 fixed)
People
(Reporter: mtabara, Assigned: nthomas)
References
Details
Attachments
(1 file)
So there's two things here:
-
Until we roll-out Dockerized scriptworkers, we're still blocked in infrastructure and we may experience long queues in signing/beetmover/balrog should we schedule all releases at once (e.g. chemspill). Because of that, we often optimized to first trigger
release
andesr
and only thenbeta
andnightly
. As far as I know, they all share the same priorities in the queue, since they are all releases. But I was wondering if there's ways we can optimize somehow, to infer different priorities (release > beta > nightly). -
The partner repacks all have the same priority but they don't all need to block the push phase. EME tasks are blocking and need to have higher priority than partner repacks counterpart, which are not blocking. I'm wondering if this is possible.
This could save us some time in the end to end release graphs, or at least reduce the time we wait until we call a certain phase.
Comment 1•5 years ago
|
||
For (1), the tasks in the graph all get a priority based on the tree here (which has release > esr > beta > nightly).
For (2), we can override that default in tasks. Looking at that list, setting the priority to low
or very-low
(based on release-level) for scriptworker release-partner tasks would likely have the desired behavior.
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 2•5 years ago
|
||
Lower the priority of partner-repack jobs and downstreams to medium, so that tasks which do block QE work are not impeded.
Updated•5 years ago
|
Pushed by nthomas@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/e8d7ad940a57 deprioritize partner-repack tasks as they don't block QE, r=aki
Comment 4•5 years ago
|
||
bugherder |
Assignee | ||
Comment 5•5 years ago
|
||
To Do - uplift to beta, release, esr68 once we ship this week.
Assignee | ||
Comment 6•5 years ago
|
||
Already on beta with the final merge from central. Other landings:
https://hg.mozilla.org/releases/mozilla-release/rev/7553d525a9ecb8069fe1af3ae075172b06e5241c
https://hg.mozilla.org/releases/mozilla-esr68/rev/2655a8f8299fb4864960abb67ce5ba1b57caea1a
Description
•