Closed
Bug 1003475
Opened 9 years ago
Closed 9 years ago
Don't do pretty names packaging on all builds
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: glandium, Assigned: glandium)
Details
Attachments
(2 files)
6.99 KB,
patch
|
bhearsum
:
review+
|
Details | Diff | Splinter Review |
1.47 KB,
patch
|
bhearsum
:
review+
|
Details | Diff | Splinter Review |
We're spending a non trivial amount of time doing most packaging steps twice, once with pretty names, and once without. This is a waste of time considering how often that breaks and how not so hard it would be to bisect if it did. As per irl discussion, let's limit them to non-unified builds.
Assignee | ||
Comment 1•9 years ago
|
||
This is the buildbot-configs part. Does this look reasonable?
Attachment #8414807 -
Flags: review?(bhearsum)
Assignee | ||
Updated•9 years ago
|
Assignee: nobody → mh+mozilla
Status: NEW → ASSIGNED
Comment 2•9 years ago
|
||
Comment on attachment 8414807 [details] [diff] [review] Only enable test_pretty_names on train branches Review of attachment 8414807 [details] [diff] [review]: ----------------------------------------------------------------- Seems ok. Needs a misc.py patch to enable for periodic builds to land though, of course.
Attachment #8414807 -
Flags: review?(bhearsum) → review+
Assignee | ||
Comment 3•9 years ago
|
||
buildbotcustom part.
Attachment #8414812 -
Flags: review?(bhearsum)
Updated•9 years ago
|
Attachment #8414812 -
Flags: review?(bhearsum) → review+
Assignee | ||
Comment 4•9 years ago
|
||
https://hg.mozilla.org/build/buildbot-configs/rev/0ca582214cda https://hg.mozilla.org/build/buildbotcustom/rev/f0926918e2a2
Assignee | ||
Comment 5•9 years ago
|
||
And a fixup https://hg.mozilla.org/build/buildbot-configs/rev/0ca582214cda.
Assignee | ||
Comment 6•9 years ago
|
||
AFAICT, it's in production since friday.
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Updated•5 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•