Sheriffing/Deciding To Close A Tree: Difference between revisions
Jump to navigation
Jump to search
(Trying to get some criteria written down for tree closures.) |
No edit summary |
||
| Line 7: | Line 7: | ||
* Broken build on an integration or main tree (e.g. mozilla-inbound, mozilla-central, fxteam) | * Broken build on an integration or main tree (e.g. mozilla-inbound, mozilla-central, fxteam) | ||
* Excessive backlog for builds or tests in any platform | * Excessive backlog for builds or tests in any platform | ||
* Infrastructure or systems failures that affect a significant number of tests or builds (e.g. AWS, data center, networking issues) | |||
Revision as of 18:39, 24 May 2016
=Deciding to close a tree
Many objective and subjective criteria are part of deciding to close a tree. Tree closure means that developers are prevented from pushing or merging code to a codebase. Later, sheriffs will reopen the trees when the problem appears to be resolved.
Some of the criteria used include:
- Broken build on an integration or main tree (e.g. mozilla-inbound, mozilla-central, fxteam)
- Excessive backlog for builds or tests in any platform
- Infrastructure or systems failures that affect a significant number of tests or builds (e.g. AWS, data center, networking issues)