Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

require fallbackMapping when backgroundRate is <100? #1086

Open
bhearsum opened this issue Dec 20, 2019 · 0 comments
Open

require fallbackMapping when backgroundRate is <100? #1086

bhearsum opened this issue Dec 20, 2019 · 0 comments
Labels
rules balrog rules and rule validation

Comments

@bhearsum
Copy link
Contributor

Now that it exists, fallbackMapping is something we almost always use when running a throttled rollout. I can't think of any case where we'd want users to go no updates instead of the previously released version during these times. We should consider enforcing this in the backend, and rejecting any requests to change backgroundRate to <100 unless fallbackMapping is set, or is getting set as part of the change.

We'll need to ensure that these would actually work for all different types of updates (GMP, SystemAddons, Firefox) before deciding to move forward.

(Imported from https://bugzilla.mozilla.org/show_bug.cgi?id=1391013)

@bhearsum bhearsum added the rules balrog rules and rule validation label Dec 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
rules balrog rules and rule validation
Projects
None yet
Development

No branches or pull requests

1 participant