Confirmed users
79
edits
Sheriffing/Deciding To Close A Tree: Difference between revisions
Sheriffing/Deciding To Close A Tree (view source)
Revision as of 10:24, 28 August 2018
, 28 August 2018no edit summary
m (Update BuildDuty to CiDuty. Renaming project) |
No edit summary |
||
| Line 11: | Line 11: | ||
In short, if the state of the tree and the surrounding systems is such that things are going to get worse if the trees stay open, it is time to close the tree. | In short, if the state of the tree and the surrounding systems is such that things are going to get worse if the trees stay open, it is time to close the tree. | ||
== Closing a tree == | |||
# Open Treeherder | |||
# Click '''Infra > TreeStatus > Login > Treestatus''' (https://mozilla-releng.net/treestatus) | |||
# Check the tree(s) you want to be closed > '''Update tree(s)''' | |||
# Status = closed; Tags = select the reason why you’re closing the tree. If “Other”, write the reason, e.g.: failures on bug 123456 | |||
# Make sure the “Remember change” option is checked | |||
# click '''Update''' | |||
== How to re-open tree(s): == | |||
# From Treestatus’ main page, you should see the closed tree(s) on the '''Recent Changes''' section. | |||
# Click the green <span style="color:#FF0000">'''Restore'''</span> button in order to re-open the trees. | |||
== Actions to take == | == Actions to take == | ||