Closed
Bug 526492
Opened 16 years ago
Closed 15 years ago
Shouldn't have to force l10n release builds if one of the en-US builds fail
Categories
(Release Engineering :: General, defect, P4)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 505392
People
(Reporter: catlee, Assigned: armenzg)
References
Details
(Whiteboard: [l10n])
I think we can use the L10n triggerable scheduler for this?
|
Assignee | |
Updated•16 years ago
|
Whiteboard: [l10n]
|
||
Comment 1•15 years ago
|
||
Mass move of bugs from Release Engineering:Future -> Release Engineering. See
http://coop.deadsquid.com/2010/02/kiss-the-future-goodbye/ for more details.
Component: Release Engineering: Future → Release Engineering
Priority: -- → P3
|
|
Assignee | |
Comment 2•15 years ago
|
||
A builder to trigger the L10n repacks without having to use http://hg.mozilla.org/build/tools/file/2f4749fe9663/buildbot-helpers/force_release_l10n.py?
Sounds like an [easy/simple] bug.
|
||
Comment 3•15 years ago
|
||
I think using Triggerable, as Catlee suggested originally, is probably a better approach. That script is mostly a hacky workaround
|
|
Assignee | |
Updated•15 years ago
|
Assignee: nobody → armenzg
Status: NEW → ASSIGNED
Priority: P3 → P4
|
|
Assignee | |
Comment 4•15 years ago
|
||
This can be fixed in bug 505392.
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
|
||
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•