Closed
Bug 1021029
Opened 10 years ago
Closed 10 years ago
add otherProductRequests support to v3 schema
Categories
(Release Engineering Graveyard :: Applications: Balrog (backend), defect)
Release Engineering Graveyard
Applications: Balrog (backend)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: bhearsum, Unassigned)
Details
(Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2360] )
We need this in the schema, and we also need the code that will process it. From bug 1013354: * we would add support in existing release blobs for definition of otherProductRequests, eg ['openh264']. This would go into to Firefox blobs, starting with those for Nightly updates * when a rule points to this type of release, Balrog will make a 'request' against itself where it substitutes the product name (ie s/Firefox/openh264/'). All the other parts of the path will be forwarded, for maximum future proofing
Reporter | ||
Comment 1•10 years ago
|
||
We probably only need this in the new v3 schema now.
Summary: add otherProductRequests support to v2 schema → add otherProductRequests support to v3 schema
Reporter | ||
Comment 2•10 years ago
|
||
We're going with two separate pings, so we don't need this right now.
No longer blocks: 1013354
Updated•10 years ago
|
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2344]
Updated•10 years ago
|
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2344] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2352]
Updated•10 years ago
|
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2352] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2360]
Reporter | ||
Comment 3•10 years ago
|
||
It doesn't look like we're going to need this after all. Openh264 is working fine without it, and EME is well on the way too.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INCOMPLETE
Updated•4 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
•