If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

make it possible to force a background check

RESOLVED FIXED

Status

Release Engineering
Balrog: Backend
P3
normal
RESOLVED FIXED
a month ago
12 days ago

People

(Reporter: bhearsum, Assigned: glasserc, Mentored)

Tracking

(Blocks: 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [lang=python])

(Reporter)

Description

a month ago
Currently, the only way to see what a background update check is getting offered is to request an URL without force=1 set (eg: https://aus5.mozilla.org/update/3/Firefox/33.0/20141202185629/Darwin_x86_64-gcc3-u-i386-x86_64/en-US/release/default/default/default/update.xml) and hope that you get on the correct side of the dice roll. This can be finnicky, and it's a hinderance to writing automated tests to verify rules.

Just like we can force a manual check by setting force=1, we should have a way to force a background check. Maybe this could be force=0, or unforce=1, or background=1.

Having this would make it easy to write tests that verify the primary and fallback mappings (just make two requests!). It wouldn't help verify that a particular background rate is set.
(Reporter)

Updated

a month ago
Priority: -- → P3
Whiteboard: [lang=python]
(Reporter)

Updated

a month ago
Blocks: 1392706
(Reporter)

Updated

a month ago
Mentor: bhearsum@mozilla.com

Comment 1

19 days ago
Hi, I want to work on this issue.
(Reporter)

Comment 2

19 days ago
(In reply to Cosm from comment #1)
> Hi, I want to work on this issue.

Unfortunately, someone has already submitted a pull request for this.
Assignee: nobody → eglassercamp

Comment 3

19 days ago
Commit pushed to master at https://github.com/mozilla/balrog

https://github.com/mozilla/balrog/commit/9653937820f2722f94bb68aa131cad66606c43b3
bug 1391668: make it possible to force a background check (#382). r=bhearsum
(Reporter)

Comment 4

13 days ago
For posterity, we ended up going with force=-1 to force a background check.
(Reporter)

Updated

13 days ago
Depends on: 1399179
(Reporter)

Comment 5

12 days ago
This is now in production - thanks Ethan!
Status: NEW → RESOLVED
Last Resolved: 12 days ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.