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

computer/api node list should include per config.xml last-modified

    Details

    • Type: New Feature
    • Status: Open (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Component/s: core
    • Labels:
    • Similar Issues:

      Description

      Currently some information about all nodes is available at once via computer/api, but O followup requests are needed to get the full node config. In some cases it makes sense to include information from the config in computer/api (JENKINS-25286). But unless the whole config is piggy backed, there will always be something missing for someone.

      By including a Last-Modified or hash of the config as a field in computer/api, it would be easy to for api clients to locally cache the node configs and avoid the O lookups

        Attachments

          Activity

          Hide
          danielbeck Daniel Beck added a comment -

          It's not clear what this is asking for. Don't depth and tree solve the issue here? Why are there O(N) followup requests?

          Show
          danielbeck Daniel Beck added a comment - It's not clear what this is asking for. Don't depth and tree solve the issue here? Why are there O(N) followup requests?
          Hide
          cburroughs Chris Burroughs added a comment -

          There is a followup request per node to get the config.xml for each node. A client first needs to know what nodes exist, before it can fetch the config.

          depth and tree control the information returned by computer/api, but the node configuration (computer/$NAME/config.xml) is not part of that api.

          Show
          cburroughs Chris Burroughs added a comment - There is a followup request per node to get the config.xml for each node. A client first needs to know what nodes exist, before it can fetch the config. depth and tree control the information returned by computer/api, but the node configuration (computer/$NAME/config.xml) is not part of that api.
          Hide
          danielbeck Daniel Beck added a comment -

          That's true.

          FWIW there's no reason this should be limited to nodes, if implemented. Anything with config.xml should be adapted accordingly.

          Show
          danielbeck Daniel Beck added a comment - That's true. FWIW there's no reason this should be limited to nodes, if implemented. Anything with config.xml should be adapted accordingly.

            People

            • Assignee:
              Unassigned
              Reporter:
              cburroughs Chris Burroughs
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: