Confirmed users
600
edits
Sheriffing/Deciding To Close A Tree: Difference between revisions
Sheriffing/Deciding To Close A Tree (view source)
Revision as of 09:14, 26 November 2024
, 26 November 2024update treestatus url
(add RelEng's and hgmo's docs on tree closures) |
m (update treestatus url) |
||
| Line 16: | Line 16: | ||
== Closing a tree == | == Closing a tree == | ||
# Open Treeherder | # Open Treeherder | ||
# Click '''Infra > TreeStatus > Login > Treestatus''' (https://mozilla | # Click '''Infra > TreeStatus > Login > Treestatus''' (https://lando.services.mozilla.com/treestatus/) | ||
# Check the tree(s) you want to be closed > '''Update tree(s)''' | # 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 | # Status = closed; Tags = select the reason why you’re closing the tree. If “Other”, write the reason, e.g.: failures on bug 123456 | ||
| Line 32: | Line 32: | ||
** If the cause is not infrastructure- or load-related, you can probably leave the Try branch and only close the affect tree, e.g. mozilla-inbound | ** If the cause is not infrastructure- or load-related, you can probably leave the Try branch and only close the affect tree, e.g. mozilla-inbound | ||
** If the cause *is* infrastructure- or load-related, you should close all trees, including Try. | ** If the cause *is* infrastructure- or load-related, you should close all trees, including Try. | ||
* Use the [https://mozilla | * Use the [https://lando.services.mozilla.com/treestatus/ TreeStatus] tool to close the affected trees. | ||
* If a bug doesn't already exist, create a bug for the tree closure. | * If a bug doesn't already exist, create a bug for the tree closure. | ||
* Communicate the tree closure to developers. Announce the closure in IRC in #developers and change the channel topic to point to the tree closure bug. This avoid several unnecessary frustrations: | * Communicate the tree closure to developers. Announce the closure in IRC in #developers and change the channel topic to point to the tree closure bug. This avoid several unnecessary frustrations: | ||