ReleaseEngineering/How To/Close or Open the Tree: Difference between revisions

no edit summary
No edit summary
No edit summary
Line 9: Line 9:
*** Edit the status text in the <span...>  
*** Edit the status text in the <span...>  
*** '''NOTE''' Do '''not''' make text up - TBPL and other tools are expecting the text given in the comment only - you will break them if you deviate.
*** '''NOTE''' Do '''not''' make text up - TBPL and other tools are expecting the text given in the comment only - you will break them if you deviate.
* Change Topic in #developers
*** make sure that you change the colour as appropriate, green for open and red for closed
* Change Topic in #developers to reflect whether trees are OPEN or CLOSED and give a bug number if appropriate
* Flush and reload Tinderbox and TBPL to confirm
* Flush and reload Tinderbox and TBPL to confirm


The following trees at minimum should be closed when there is a general infrastructure problem
* [http://tinderbox.mozilla.org/admintree.cgi?tree=Firefox Firefox]
* [http://tinderbox.mozilla.org/admintree.cgi?tree=Firefox Firefox]
* [http://tinderbox.mozilla.org/admintree.cgi?tree=Firefox3.6 Firefox 3.6]
* [http://tinderbox.mozilla.org/admintree.cgi?tree=Firefox3.5 Firefox 3.5]
* [http://tinderbox.mozilla.org/admintree.cgi?tree=MozillaTry Try]
* [http://tinderbox.mozilla.org/admintree.cgi?tree=MozillaTry Try]
* [http://tinderbox.mozilla.org/showbuilds.cgi?tree=Mozilla-Inbound Mozilla-Inbound]
Confirmed users
1,377

edits