Closed Bug 678467 Opened 9 years ago Closed 7 years ago

Mobile partner repacks should be triggered automatically

Categories

(Release Engineering :: Release Automation: Other, defect, P3)

x86
Linux
defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: rail, Unassigned)

Details

(Whiteboard: [releases][automation][mobile])

Attachments

(1 file)

Mobile partner repacks scheduler shouldn't wait for post_l10n branch and probably may be triggered at the end of build (since there is no l10n repacks).
What mobile partners do we have? Ovi store is going away after 7.0 AFAIK.
Priority: -- → P3
(In reply to Chris Cooper [:coop] from comment #1)
> What mobile partners do we have? Ovi store is going away after 7.0 AFAIK.

Yeah.
There are rumblings about Android partner repacks but that hasn't materialized.
Am I on the right track?
Attachment #555840 - Flags: feedback?(rail)
Comment on attachment 555840 [details] [diff] [review]
passes test-masters, not sure if it'll work

It looks fine. However, instead of using Dependants I'd prefer to use Triggerables and trigger them as a last step. In this case repacks will be triggered in any case, even if you force a builder.
Attachment #555840 - Flags: feedback?(rail) → feedback+
No longer blocks: hg-automation
Mass move of bugs to Release Automation component.
Component: Release Engineering → Release Engineering: Automation (Release Automation)
No longer blocks: hg-automation
17:00 < aki> we haven't done a mobile partner repack ever
17:00 < rail> yeah
17:00 < rail> kill it
17:00 < aki> so it's still not triggered automatically, but not sure we need it
17:00 < aki> s,done,shipped,
17:00 < aki> i think i did one the first release or two, never shipped
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.