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

keep slaves information outside of config.xml file

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      I'm using JClouds plugin with Openstack to manage Jenkins slaves.
      new VMs are created and old ones are destroyed all the time.
      this leads to config.xml file being constantly updated with the slave nodes info.

      we backup Jenkins config files to Git every 15 minutes.
      this leads to config.xml file history being cluttered with all these slave changes...

      if slaves info could be moved out from global/config.xml to a separate file like slaves.xml or something, that would greatly simplify checking what was changed in config.xml recently - in case you need to troubleshoot a problem...

        Attachments

          Activity

          Hide
          felfert Fritz Elfert added a comment -

          Huh? Can you be more specific about how you use JClouds?
          At least here with current stable LTS I can not see this behavior!

          The running nodes are stored in a separate location:

          $JENKINS_HOME/nodes/<nodename>/config.xml
          

          Furthermore: If this is different with some old jenkins version, it is a core issue, because the jclouds plugin has no
          influence about where the core persists running nodes. It just invokes Jenkins.getInstance().addNode(...) after creating
          a slave (in order to make it available to jenkins).

          Show
          felfert Fritz Elfert added a comment - Huh? Can you be more specific about how you use JClouds? At least here with current stable LTS I can not see this behavior! The running nodes are stored in a separate location: $JENKINS_HOME/nodes/<nodename>/config.xml Furthermore: If this is different with some old jenkins version, it is a core issue, because the jclouds plugin has no influence about where the core persists running nodes. It just invokes Jenkins.getInstance().addNode(...) after creating a slave (in order to make it available to jenkins).
          Hide
          alskor Alex Java added a comment -

          we are using Jenkins 1.580.3. I guess this is just an old version...

          Show
          alskor Alex Java added a comment - we are using Jenkins 1.580.3. I guess this is just an old version...
          Hide
          felfert Fritz Elfert added a comment -

          Obviously an outdated jenkins core (the persistence layer is in the core anyway).

          Show
          felfert Fritz Elfert added a comment - Obviously an outdated jenkins core (the persistence layer is in the core anyway).

            People

            • Assignee:
              felfert Fritz Elfert
              Reporter:
              alskor Alex Java
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: