Closed
Bug 535896
Opened 15 years ago
Closed 15 years ago
move release automation out of master-main.cfg
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: lsblakk, Assigned: lsblakk)
References
Details
Attachments
(1 file)
|
9.32 KB,
patch
|
bhearsum
:
review+
|
Details | Diff | Splinter Review |
and into master1.cfg/master2.cfg so it's not on all buildmaster instances - for example the upcoming try as a branch.
|
Assignee | |
Comment 1•15 years ago
|
||
tested in staging quickly, no issues. this is mostly to help with the addition of a master3.cfg to use in tryserver once it's a branch in config.py.
Attachment #418745 -
Flags: review?(nrthomas)
|
|
Assignee | |
Updated•15 years ago
|
Attachment #418745 -
Flags: review?(nrthomas) → review?(bhearsum)
|
||
Comment 2•15 years ago
|
||
Comment on attachment 418745 [details] [diff] [review] move release automation to master1/master2 out of master-main This should be OK. By the looks of it, it doesn't change the order we do our imports in any meaningful way, so I can't see us hitting any reconfig issues. Let's just be sure not to land this while a release is running, out of paranoia
Attachment #418745 -
Flags: review?(bhearsum) → review+
|
|
Assignee | |
Comment 3•15 years ago
|
||
http://hg.mozilla.org/build/buildbot-configs/rev/53567249d3d0
|
|
Assignee | |
Updated•15 years ago
|
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
|
||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•