-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
Jenkins 1.580.3
I created a new slave/worker node in my Jenkins,
then some job started running on it.
then I edited the Jenkins node settings: changed its IP address and clicked save.
I didn't check if there was something running on that node at the time... apparently there was. oh well..
I was hoping that worst case jenkins would just abort that job after some timeout and then reuse that new worker. also, there was "abort if stuck" setting on that job (coming from a jenkins plugin).
but what happened was that even 2 days later the build job was still "running" and clicking "abort" had no effect. I tried clicking that red button many times - no effect.
I had to restart the master jenkins instance for those jobs to finally stop.
jenkins should gracefully handle situations when the slave/worker node disappears - like in this case when I changed the IP address of the node while there was something running on it (essentially I wanted to rename the worker...)