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

From MozillaWiki
Jump to navigation Jump to search
(add gaia closing/opening instructions)
m (minor format update)
 
(9 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{Release Engineering How To|Close or Open the Tree}}
{{Release Engineering How To|Close or Open the Tree}}


* Warn #developers IRC channel and the [[Sheriffing#Meet_the_Sheriffs|sheriffs]].
===== What to do in case if you need to close the trees =====
* Use https://treestatus.mozilla.org/ to close the trees.  
 
* Warn #developers IRC channel and the [[Sheriffing#Meet_the_Sheriffs|#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).
** 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).
** 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.
* Reload TreeStatus to confirm the status has changed.


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
* autoland
* mozilla-central
* mozilla-central
* mozilla-inbound
* mozilla-inbound
* mozilla-aurora
* mozilla-beta
* mozilla-beta
* mozilla-esr*
* mozilla-esr*
* mozilla-b2g*
 
* gaia -- treestatus plus the following:
===== How to open/close the trees =====
** While Gaia is listed on Treestatus, it's a no-op closure from there (mainly useful to consumers of the Treestatus API for knowing the current state).
 
** To actually close Gaia, someone in the Owners group will need to go the Github settings page and remove the Chefs and Cooks teams from the [https://github.com/mozilla-b2g/gaia/settings/collaboration collaborators listing]
Go to TreeStatus page https://mozilla-releng.net/treestatus
** Once the event is over, those teams can be re-added to "open" Gaia once again.
 
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]

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 .


Tree screen2.png


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


Tree screen3.png


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.


Tree screen4.png


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

Retrieved from "https://wiki.allizom.org/index.php?title=ReleaseEngineering/How_To/Close_or_Open_the_Tree&oldid=1211628"