Closed
Bug 370354
Opened 18 years ago
Closed 17 years ago
need bonsai trees for the 1.8 and 1.8.0 branches
Categories
(mozilla.org Graveyard :: Server Operations, task)
mozilla.org Graveyard
Server Operations
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: dbaron, Assigned: justdave)
References
()
Details
This has been annoying people for quite a while, but I'm don't think anyone's filed a bug on it. We need a bonsai "tree" for the 1.8 branch and one for the 1.8.0 branch so we can set open/closed state on those branches. I don't currently see one in http://bonsai.mozilla.org/switchtree.cgi (Once we have one, it's pretty easy to edit the tinderbox configs to point at the appropriate tree -- I think it's even be doable from the tinderbox UI, but I'd honestly guess that that's riskier.)
Assignee | ||
Comment 1•17 years ago
|
||
Looks like in order to add a tree to bonsai, I need to match it to a module in CVS. Can you run cvs co -c on the cvs server and tell me if any of the existing modules are appropriate? The Seamonkey 1.0 Branch tree uses MozillaBranchTinderboxAll, which appears to only differ from MozillaTinderboxAll by the addition of NSS and NSPR. Is that one appropriate to use, or do we need to create another one?
Assignee | ||
Updated•17 years ago
|
Assignee: server-ops → justdave
Assignee | ||
Updated•17 years ago
|
Whiteboard: waiting for CVS tree info from reporter
Reporter | ||
Comment 2•17 years ago
|
||
The module to use is AviarySuiteBranchTinderbox.
Assignee | ||
Updated•17 years ago
|
Whiteboard: waiting for CVS tree info from reporter
Assignee | ||
Comment 3•17 years ago
|
||
OK, this is done. Find me or file another bug when you want to mess with Tinderbox.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Updated•9 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•