Closed
Bug 498654
Opened 16 years ago
Closed 15 years ago
Re-enable timely l10n repacks
Categories
(Release Engineering :: General, defect, P4)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Pike, Assigned: armenzg)
References
Details
(Keywords: regression, Whiteboard: [l10n])
Bug 498468 made the l10n repacks trigger at most every 15 minutes, that ain't quick enough.
We should get those builds back up to quick responses as soon as feasible.
|
Reporter | |
Updated•16 years ago
|
Keywords: regression
Whiteboard: [l10n]
|
|
||
Comment 1•16 years ago
|
||
A great way to do this would be to have commit hooks in the hg repos that can create a buildbot sendchange to our buildbot master.
Or, have a separate process that polls the repositories and does the equivalent sendchange.
In either case the master process isn't bogged down with polling and parsing the hg change information.
|
||
Updated•16 years ago
|
Component: Release Engineering → Release Engineering: Future
|
||
Comment 2•16 years ago
|
||
Another option (discussed further down the dependency chain) is bug 498641 (cross-repo pushlog for l10n).
|
|
||
Comment 3•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 | |
Updated•15 years ago
|
Assignee: nobody → armenzg
Status: NEW → ASSIGNED
Priority: P3 → P4
|
|
Assignee | |
Comment 4•15 years ago
|
||
This got fixed recently with this:
http://hg.mozilla.org/build/buildbotcustom/diff/30499aa7f126/misc.py
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
|
||
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
•