Closed
Bug 531414
Opened 16 years ago
Closed 16 years ago
Tidy up builder mozconfigs (reorganise directory structure)
Categories
(Mozilla Messaging Graveyard :: Release Engineering, defect)
Mozilla Messaging Graveyard
Release Engineering
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: standard8, Assigned: gozer)
References
Details
Attachments
(1 file)
|
8.63 KB,
patch
|
Details | Diff | Splinter Review |
As I keep on having to play with mozconfigs, the current structure is a bit messy and hard to remember where things are as some mozconfigs are in a branch specific location, some aren't, and some are effectively duplicated with one being redundant.
Especially as we've got a 1.9.2 branch coming soon, I'd like to just tidy this up so that we pretty much match how Firefox does their mozconfigs:
<platform>/<branch>/<buildtype>
Where buildtype is one of nightly, unittest, debug, release.
The patch does the necessary changes to the mozconfig locations and the buildbot config.
It also moves the calendar and sunbird mozconfigs to be underneath <platform>/<branch>, but doesn't go further as I couldn't decide how ;-) (but IMHO it is good enough for now).
There's also a couple of fixes/tidy ups to the mozconfigs as well.
Attachment #414856 -
Flags: review?(gozer)
| Assignee | ||
Comment 1•16 years ago
|
||
Comment on attachment 414856 [details] [diff] [review]
The fix
Looks good, but it's always tricky to tell with buildbot. I suggest applying to staging on monday, and see how it goes before pushing to production.
| Reporter | ||
Comment 2•16 years ago
|
||
Yep, fine by me.
| Reporter | ||
Comment 3•16 years ago
|
||
Shifting to gozer for picking up once releases are a bit quieter.
Assignee: bugzilla → gozer
| Assignee | ||
Updated•16 years ago
|
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
| Reporter | ||
Comment 4•16 years ago
|
||
Comment on attachment 414856 [details] [diff] [review]
The fix
Clearing request now this is fixed ;-)
Attachment #414856 -
Flags: review?(gozer)
You need to log in
before you can comment on or make changes to this bug.
Description
•