Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-13441

Slave status information shouldn't be stored in main config file

XMLWordPrintable

      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.

          [JENKINS-13441] Slave status information shouldn't be stored in main config file

          Jacob Robertson added a comment -

          Configuration slicing does not in any way influence where/how the configuration is saved. Removing that component.

          Jacob Robertson added a comment - Configuration slicing does not in any way influence where/how the configuration is saved. Removing that component.

          Oleg Nenashev added a comment -

          Agent configuration have been removed from Jenkins config.xml somewhere in Jenkins 1.x

          Oleg Nenashev added a comment - Agent configuration have been removed from Jenkins config.xml somewhere in Jenkins 1.x

            mdonohue mdonohue
            berlincount Andreas Kotes
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: