[JENKINS-23581] node configuration change should relaunch slave

when i change the configuration of a slave, the slave should relaunch itself to adopt the new configuration, or a flag/message should be shown that the config is out of date on that node (updated since launch).

For instance, if I change the host or port for the slave, and then run a job, I expect that job to run on the new host.

However, I accept there may be times when I want to defer the launch (for instance to launch all slaves at a cutover time), so a warning that the slave needs to be re-launched may be a suitable compromise.

---
Originally reported by charlie_ecc, imported from: node configuration change should relaunch slave

• assignee: kohsuke
  
• status: Open
  
• priority: Major
  
• component(s): slave-setup-plugin
  
• label(s): config, slaves
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 1
  
• imported: 20251216-225446
  

Raw content of original issue

when i change the configuration of a slave, the slave should relaunch itself to adopt the new configuration, or a flag/message should be shown that the config is out of date on that node (updated since launch).


For instance, if I change the host or port for the slave, and then run a job, I expect that job to run on the new host.


However, I accept there may be times when I want to defer the launch (for instance to launch all slaves at a cutover time), so a warning that the slave needs to be re-launched may be a suitable compromise.

• environment: Linux version 3.2.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.2.57-3+deb7u2