Closed Bug 498654 Opened 11 years ago Closed 9 years ago

Re-enable timely l10n repacks

Categories

(Release Engineering :: General, defect, P4)

defect

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.
Keywords: regression
Whiteboard: [l10n]
Depends on: 493752
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.
Component: Release Engineering → Release Engineering: Future
Another option (discussed further down the dependency chain) is bug 498641 (cross-repo pushlog for l10n).
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: nobody → armenzg
Status: NEW → ASSIGNED
Priority: P3 → P4
This got fixed recently with this:
http://hg.mozilla.org/build/buildbotcustom/diff/30499aa7f126/misc.py
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.