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

Latest revision as of 14:14, 2 May 2019

What to do in case if you need to close the trees

Warn #developers IRC channel and the #sheriffs.
Use https://mozilla-releng.net/treestatus 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).
- Set the topic in #ci with the following model: OnDuty: --- ldap --- ALL/ (Name of the trees) CURRENTLY CLOSED --- BUG: bug number --- Unified #releng / #buildduty channels. CI issues? You’ve come to the right place. | This channel is logged at https://mozilla.logbot.info/ci
Reload TreeStatus to confirm the status has changed.

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

autoland
mozilla-central
mozilla-inbound
mozilla-beta
mozilla-esr*

How to open/close the trees

Go to TreeStatus page https://mozilla-releng.net/treestatus

Log on with your LDAP account in order to be able to open/close trees .

Select the trees in question and click on Update tree(s).

On this page select the new Status you'd like the tree(s) to have. Fill out the Reason bar with a comment about why are you closing the tree/trees, then click Update in order to submit the changes.

For more information about tree closer procedure please also check : Incident management for Firefox infrastructure related tree-closures

@@ Line 1: / Line 1: @@
 {{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)
+===== What to do in case if you need to close the trees =====
-* Warn #developers IRC channel
-* for each tree you want to close (full list of interesting trees is under "More" on TBPL):
+* Warn #developers IRC channel and the [[Sheriffing#Meet_the_Sheriffs|#sheriffs]].
-** go to http://tinderbox.mozilla.org/admintree.cgi?tree=$treename (see quick links below), and
+* Use https://mozilla-releng.net/treestatus to close the trees.
-*** find the "Status message" edit box - the second one
+** 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).
-*** '''READ''' the comments in the edit box, if any
+** In order to change tree statuses, your browserID email needs to be added with sheriff permissions (ping edmorley/philor/catlee or ask in #developers).
-*** Edit the status text in the &lt;span...&gt;
+** Set the topic in #ci with the following model:  OnDuty: --- ldap --- ALL/ (Name of the trees) CURRENTLY CLOSED --- BUG: bug number --- Unified #releng / #buildduty channels. CI issues? You’ve come to the right place. | This channel is logged at https://mozilla.logbot.info/ci
-*** '''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.
+* Reload TreeStatus to confirm the status has changed.
-*** 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
-* [http://tinderbox.mozilla.org/admintree.cgi?tree=Firefox Firefox]
+* autoland
-* [http://tinderbox.mozilla.org/admintree.cgi?tree=MozillaTry Try]
+* mozilla-central
-* [http://tinderbox.mozilla.org/showbuilds.cgi?tree=Mozilla-Inbound Mozilla-Inbound]
+* mozilla-inbound
+* mozilla-beta
+* mozilla-esr*
+===== How to open/close the trees =====
+Go to TreeStatus page https://mozilla-releng.net/treestatus
+Log on with your LDAP account in order to be able to open/close trees .
+[[File:Tree screen2.png|800px]]
+Select the trees in question and click on Update tree(s).
+[[File:Tree screen3.png|800px]]
+On this page select the new Status you'd like the tree(s) to have. Fill out the Reason bar with a comment about why are you closing the tree/trees, then click Update in order to submit the changes.
+[[File:Tree screen4.png|800px]]
+For more information about tree closer procedure please also check : [https://docs.google.com/document/d/12EVlfE79G9Jceeu_YjFWjCm4Q4-dglzSGZEYqKTyDs8/edit?pli=1#heading=h.nv4u9u7iq12x Incident management for Firefox infrastructure related tree-closures]