|
Another issue I have is similar.
Say a slave is for some label "node" and goes offline. If no other slave has the label "node" then that label isn't remembered by the Jenkins system. Thus, when a job is edited and saved, it removes the label from the configuration permanently (as it doesn't exist according to the master). This happens for example with a matrix job.
This is a problem if someone happens to edit a job during a window when a slave is offline, and results in a hidden loss of running on that slave in the matrix job builds.
|