Closed Bug 1113462 Opened 7 years ago Closed 7 years ago

Add partner build special cases to Balrog

Categories

(Release Engineering :: Release Requests, defect)

x86
All
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: nthomas, Unassigned)

References

Details

Attachments

(1 file)

Bug 1110301 and bug 1113455 added special handling for partner builds. We should implement that in Balrog to enable the switchover.
The combination of those two bugs appears to be:
- Block all mac partner builds from updating at all (including en-US).
- Point other platforms' en-US partner builds at 34.0 (instead of 34.0.5).
- All other platforms' l10n partner builds are unaffected (ie, they point at 34.0.5 right now, and will point at 35.0 when we ship it).
Attached file verification output
(In reply to Ben Hearsum [:bhearsum] from comment #1)
> The combination of those two bugs appears to be:
> - Block all mac partner builds from updating at all (including en-US).

This is satisfied with a rule as follows:
product: Firefox, channel: release-cck*, Background Rate: 100, priority: 100, OS Version: Darwin, mapping: No-Update

(I used OS Version instead of Build Target because OS Version supports substring matching.)

> - Point other platforms' en-US partner builds at 34.0 (instead of 34.0.5).

And this with:
product: Firefox, channel: release-cck*, Background Rate: 100, Priority: 97, locale: en-US, mapping: Firefox-34.0-build2

> - All other platforms' l10n partner builds are unaffected (ie, they point at
> 34.0.5 right now, and will point at 35.0 when we ship it).

The rest of these fall through to the existing rules, didn't need to do anything special for them.

Attached is a bunch of URLs + curl output that I used to verify. I wouldn't mind a second set of eyes on it.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.