ReleaseEngineering/How To/Close or Open the Tree: Difference between revisions
< ReleaseEngineering | How To
Jump to navigation
Jump to search
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=MozillaTry Try] | * [http://tinderbox.mozilla.org/admintree.cgi?tree=MozillaTry Try] | ||
* [http://tinderbox.mozilla.org/showbuilds.cgi?tree=Mozilla-Inbound Mozilla-Inbound] | |||
Revision as of 21:07, 11 February 2012
- Warn the sheriff (the main Tinderbox page lists who it currently is, as does TBPL in the "Tree Info" dropdown)
- Warn #developers IRC channel
- for each tree you want to close (full list of interesting trees is under "More" on TBPL):
- go to http://tinderbox.mozilla.org/admintree.cgi?tree=$treename (see quick links below), and
- find the "Status message" edit box - the second one
- READ the comments in the edit box, if any
- 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.
- make sure that you change the colour as appropriate, green for open and red for closed
- go to http://tinderbox.mozilla.org/admintree.cgi?tree=$treename (see quick links below), and
- 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
The following trees at minimum should be closed when there is a general infrastructure problem