-
-
Notifications
You must be signed in to change notification settings - Fork 23
Description
changes done to org.jenkinsci.plugins.slave_setup.SetupConfig.xml on disk is not reflected in the running jenkins process when reload-configuration is triggered trough the cli. restarting jenkins makes the changes appear on new slaves.
so we have some configuration in org.jenkinsci.plugins.slave_setup.SetupConfig.xml that we altered during our jenkiins deployment process. the changes where pressent on the filesystem. But jenkins slave plugin continued to provision new slaves with the old config after reload-configuration had been called trough the cli. Restarting jenkins made the change appear.
I would have expected that the reload configuration had also updated the configuration of the slave setup plugin
Originally reported by
fvissing, imported from: the slave_setup plugin does not reload its configuration from disk when reload-configuration is triggered from the jenkins cli
- assignee:
peppe
- status: Open
- priority: Minor
- component(s): slave-setup-plugin
- label(s): plugin, slave
- resolution: Unresolved
- votes: 0
- watchers: 2
- imported: 20251216-225446
Raw content of original issue
changes done to org.jenkinsci.plugins.slave_setup.SetupConfig.xml on disk is not reflected in the running jenkins process when reload-configuration is triggered trough the cli. restarting jenkins makes the changes appear on new slaves.
so we have some configuration in org.jenkinsci.plugins.slave_setup.SetupConfig.xml that we altered during our jenkiins deployment process. the changes where pressent on the filesystem. But jenkins slave plugin continued to provision new slaves with the old config after reload-configuration had been called trough the cli. Restarting jenkins made the change appear. I would have expected that the reload configuration had also updated the configuration of the slave setup plugin
environment
jenkins lts 2.235.5-1.1 running on centos 7 based host<br/>
slave setup plugin 1.10<br/>