Closed
Bug 1282891
Opened 8 years ago
Closed 8 years ago
support fallback mappings when background rate roll fails
Categories
(Release Engineering Graveyard :: Applications: Balrog (backend), defect)
Release Engineering Graveyard
Applications: Balrog (backend)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bhearsum, Assigned: ninad101, Mentored)
References
Details
In talks about how to do throttled rollouts for Go Faster we came up with the idea of having a "fallback" mapping - a release that would be returned if a user is on the wrong side of a background rate dice roll. This would let us do things such as roll out an updated version of Hello at a low rate, while still returning the latest released version to everyone else (in case they aren't up to date already). This would probably be useful for Firefox when we're doing throttled rollouts as well.
Reporter | ||
Comment 1•8 years ago
|
||
Ninad has been working on this in https://github.com/mozilla/balrog/pull/160.
Assignee: nobody → bhat.ninadmb
Comment 2•8 years ago
|
||
Commit pushed to master at https://github.com/mozilla/balrog
https://github.com/mozilla/balrog/commit/2b4eab7acccc089419ed0ec87c92089e5798dea6
Bug 1282891: support fallback mappings when background rate roll fails (#160). r=bhearsum
Reporter | ||
Comment 3•8 years ago
|
||
This is in production, thanks Ninad!
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Updated•8 years ago
|
Updated•5 years ago
|
Product: Release Engineering → Release Engineering Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•