Closed
Bug 1400079
Opened 7 years ago
Closed 7 years ago
Reduce Thunderbird Nightly Locale Count
Categories
(Release Engineering :: General, enhancement)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Callek, Assigned: Callek)
References
Details
Attachments
(1 file)
Recently releng discovered that our largest spending in AWS, at least for build related jobs, are coming from perma-failing Thunderbird nightly repacks.
Unless there are compelling reasons not to, on Monday, Sept 18th, we will proceed with disabling all but a few busted jobs. Once the remaining jobs running are green again, we can start re-enabling all locales.
The goal here is to avoid spending extra money on things that are perma-busted rather than to hinder your ability to debug and fix.
=====
The technical details of this work will be to greatly reduce the number of locales we will attempt to repack, we can back that out once the jobs are fixed.
Comment 1•7 years ago
|
||
This would only affect the locales lists in buildbot-configs, right?
Flags: needinfo?(bugspam.Callek)
Assignee | ||
Comment 2•7 years ago
|
||
(In reply to Axel Hecht [:Pike] from comment #1)
> This would only affect the locales lists in buildbot-configs, right?
Correct this would be the all-locales.comm-central file which is used: https://dxr.mozilla.org/build-central/source/buildbot-configs/mozilla/thunderbird_config.py?q=comm-central+all-locales&redirect_type=single#738 --> https://dxr.mozilla.org/build-central/source/buildbotcustom/l10n.py#92
Flags: needinfo?(bugspam.Callek)
Comment hidden (mozreview-request) |
Comment 4•7 years ago
|
||
mozreview-review |
Comment on attachment 8909431 [details]
Bug 1400079 - Reduce Thunderbird Nightly Locale Count.
https://reviewboard.mozilla.org/r/180934/#review186256
Attachment #8909431 -
Flags: review?(catlee) → review+
Assignee | ||
Comment 5•7 years ago
|
||
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Updated•7 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•