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

From MozillaWiki
Jump to navigation Jump to search
No edit summary
(Adjust instructions now that we've switched to treestatus)
Line 1: Line 1:
{{Release Engineering How To|Close or Open the Tree}}
{{Release Engineering How To|Close or Open the Tree}}


* Warn the sheriff (the main [http://tinderbox.mozilla.org/showbuilds.cgi?tree=Firefox Tinderbox] page lists who it currently is, as does TBPL in the "Tree Info" dropdown)
* Warn #developers IRC channel and edmorley/philor/mbrubeck/RyanVM/ehsan
* Warn #developers IRC channel
* Use https://treestatus.mozilla.org/ to close the trees.  
* for each tree you want to close (full list of interesting trees is under "More" on TBPL):
** Please use the "Remember previous state" option, so you can easily restore the previous status messages when you are finished (there will be a restore button at the bottom of the page).
** go to http://tinderbox.mozilla.org/admintree.cgi?tree=$treename (see quick links below), and
** In order to change tree statuses, your browserID email needs to be added with sheriff permissions (ping edmorley/philor/catlee or ask in #developers).
*** find the "Status message" edit box - the second one
* Change Topic in #developers to reflect whether trees are OPEN or CLOSED and give a bug number if appropriate.
*** '''READ''' the comments in the edit box, if any
* Reload TBPL to confirm the status has changed.
*** 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
* 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
The following trees at minimum should be closed when there is a general infrastructure problem
* [http://tinderbox.mozilla.org/admintree.cgi?tree=Firefox Firefox]
* mozilla-central
* [http://tinderbox.mozilla.org/admintree.cgi?tree=MozillaTry Try]
* mozilla-inbound
* [http://tinderbox.mozilla.org/showbuilds.cgi?tree=Mozilla-Inbound Mozilla-Inbound]
* mozilla-aurora
* mozilla-beta
* mozilla-esr10
* try

Revision as of 19:56, 21 August 2012


  • Warn #developers IRC channel and edmorley/philor/mbrubeck/RyanVM/ehsan
  • Use https://treestatus.mozilla.org/ to close the trees.
    • Please use the "Remember previous state" option, so you can easily restore the previous status messages when you are finished (there will be a restore button at the bottom of the page).
    • In order to change tree statuses, your browserID email needs to be added with sheriff permissions (ping edmorley/philor/catlee or ask in #developers).
  • Change Topic in #developers to reflect whether trees are OPEN or CLOSED and give a bug number if appropriate.
  • Reload TBPL to confirm the status has changed.

The following trees at minimum should be closed when there is a general infrastructure problem

  • mozilla-central
  • mozilla-inbound
  • mozilla-aurora
  • mozilla-beta
  • mozilla-esr10
  • try
Retrieved from "https://wiki.allizom.org/index.php?title=ReleaseEngineering/How_To/Close_or_Open_the_Tree&oldid=462895"