docs/ci: rewrite the "farm maintenance ^ other change" rule to mean what we actually meant
Sometimes updates to the farm config are needed before re-enabling it, or updating test expectations with new failures that happened while the farm was down, etc. These need to be allowed, as the alternative is to update the config/expectations/etc. blindly in one MR, merge it, and then merge another MR with the farm re-enablement. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25560>
This commit is contained in:

committed by
Marge Bot

parent
6d6d0b515e
commit
b72f474ff0
@@ -59,7 +59,8 @@ Farm management
|
||||
---------------
|
||||
|
||||
.. note::
|
||||
Never mix farm maintenance with any other change in the same merge request!
|
||||
Never mix disabling/re-enabling a farm with any change that can affect a job
|
||||
that runs in another farm!
|
||||
|
||||
When the farm starts failing for any reason (power, network, out-of-space), it needs to be disabled by pushing separate MR with
|
||||
|
||||
|
Reference in New Issue
Block a user