Closed Bug 1149544 Opened 9 years ago Closed 3 years ago

only submit necessary bouncer entries for each channel

Categories

(Release Engineering :: Release Automation: Bouncer, defect, P5)

Product:
Release Engineering
Component:
Release Automation: Bouncer
Platform:
x86_64
Linux
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: bhearsum, Unassigned)

Details

bug 1105485 added support for shipping a release to multiple channel. Unfortunately, the bouncer submitter and uptake check steps don't deal with channel-specific entries. For example, when we built 37.0build2 we submitted bouncer entries like "Firefox-37.0build2-Partial-36.0.4build1", which point to locations like "/firefox/candidates/37.0-candidates/build2/update/win32/:lang/firefox-36.0.4-37.0.partial.mar" - which are entirely unnecessary, as those only ship on the release channel, which uses "Firefox-37.0build2-Partial-36.0.4" (which points at the releases dir).
Priority: -- → P5
Component: Release Automation: Other → Release Automation: Bouncer

I believe this bug outlived its usefulness.

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.