[
https://issues.jenkins-ci.org/browse/JENKINS-13441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jacob_robertson updated JENKINS-13441:
--------------------------------------
Component/s: (was: configurationslicing)
Configuration slicing does not in any way influence where/how the configuration
is saved. Removing that component.
> Slave status information shouldn't be stored in main config file
> ----------------------------------------------------------------
>
> Key: JENKINS-13441
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13441
> Project: Jenkins
> Issue Type: Improvement
> Components: master-slave, slave-status
> Affects Versions: current
> Reporter: Andreas Kotes
> Assignee: mdonohue
>
> Jenkins stores slave information as well as their status in the main config
> file. As we've automated the configuration via Puppet, any automated changes
> trigger and overwrite and service restart (if not handled properly). Such is
> the case for slave state changes, e.g. when a slave goes offline due to disk
> usage issues.
> Suggestion: split of slave configuration (or at least their status
> information) into a separate configuration file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
