Closed
Bug 394494
Opened 17 years ago
Closed 17 years ago
Command line way to determine mirror absorption of a product
Categories
(Release Engineering :: General, defect, P3)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 408673
People
(Reporter: joduinn, Unassigned)
References
Details
Bug#390201 lets us see the % mirror absorption a new product has currently. This lets us accurately see whether we can safely proceed to the next step in the build/release process. Can we get the same functionally wrapped inside of a command line utility, so we could automate it as part of the build/release process? Its unclear whether it would be better to have this: - return a boolean (true=go, false=nogo) which means keeping the trigger threshold within bouncer. or - return an integer (% mirror absorption) which means keeping the trigger threshold within the build automation systems someplace. Regardless of where the threshold is kept, there is also the question of "what should the threshold be?" Recent SWAG by justin and joduinn put it in the 75%-80%, which worked fine for a recent TB release, but this is just a SWAG. This was discussed late at night during the recent allhands by morgamic and joduinn, but there are still many details to work out, hence this tracking bug.
Reporter | ||
Updated•17 years ago
|
Comment 1•17 years ago
|
||
(In reply to comment #0) > Can we get the same functionally wrapped inside of a command line utility, so > we could automate it as part of the build/release process? I'm confused... what exactly do we want automated here?
Updated•17 years ago
|
Assignee: build → nobody
QA Contact: mozpreed → build
Reporter | ||
Updated•17 years ago
|
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•