![]() |
|
|
|
|
Issue Type:
|
![Improvement]() Improvement
|
|
Affects Versions:
|
current |
|
Assignee:
|
Kohsuke Kawaguchi
|
|
Components:
|
slave-setup |
|
Created:
|
26/Jun/14 1:31 AM
|
|
Description:
|
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 ([email protected]) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.2.57-3+deb7u2
|
|
Project:
|
Jenkins
|
|
Labels:
|
slaves
config
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Charlie Stott
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[email protected].
For more options, visit
https://groups.google.com/d/optout.
