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

From MozillaWiki
Jump to navigation Jump to search
(Created page with "{{Release Engineering How To|Close or Open the Tree}} See [https://intranet.mozilla.org/RelEngWiki/index.php/BuildDuty#How_do_I_close_the_tree.3F BuildDuty] (auth required)")
 
No edit summary
Line 1: Line 1:
{{Release Engineering How To|Close or Open the Tree}}
{{Release Engineering How To|Close or Open the Tree}}
See [https://intranet.mozilla.org/RelEngWiki/index.php/BuildDuty#How_do_I_close_the_tree.3F BuildDuty] (auth required)
 
* 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
* 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.
* Change Topic in #developers
* Flush and reload Tinderbox and TBPL to confirm
 
* [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]

Revision as of 21:00, 18 August 2011


  • 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.
  • Change Topic in #developers
  • Flush and reload Tinderbox and TBPL to confirm