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

tie-matrix-parent plugin GUI

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Won't Fix
    • Icon: Major Major
    • matrix-project-plugin
    • None

      Could you make the GUI look like in "Build on multiple nodes", ie having a tree-view with "nodes" and "labels" on the first level. This is easier as the plain list with everything.

          [JENKINS-7016] tie-matrix-parent plugin GUI

          Axel Heider created issue -

          kbertelson added a comment -

          You bring up a good point. I can see this becoming difficult to deal with if you have many nodes and labels. However, I tried to make this mimic the existing GUI of Hudson as much as I could. The Hudson native feature: "Tie this project to node" was my inspiration. It ties nodes for freestyle, non-Matrix jobs with a drop-down list, too.

          I suppose that the best way to deal with many entries, is to use the control's awareness of the starting letter of each entry: If you type 's', it will instantly select the next node/lable that begins with 's'.

          kbertelson added a comment - You bring up a good point. I can see this becoming difficult to deal with if you have many nodes and labels. However, I tried to make this mimic the existing GUI of Hudson as much as I could. The Hudson native feature: "Tie this project to node" was my inspiration. It ties nodes for freestyle, non-Matrix jobs with a drop-down list, too. I suppose that the best way to deal with many entries, is to use the control's awareness of the starting letter of each entry: If you type 's', it will instantly select the next node/lable that begins with 's'.
          kbertelson made changes -
          Resolution New: Won't Fix [ 2 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]

          Axel Heider added a comment -

          Your answer is valid. However, I'll try bringing up this isse in a more general way with JENKINS-7028 then. From my experience, forning a special naming scheme on things just to make the certain GUI list behave better is a bad approach in the long term. This mixes up different aspects that could easily be addressed in the appropriate modules.

          Axel Heider added a comment - Your answer is valid. However, I'll try bringing up this isse in a more general way with JENKINS-7028 then. From my experience, forning a special naming scheme on things just to make the certain GUI list behave better is a bad approach in the long term. This mixes up different aspects that could easily be addressed in the appropriate modules.
          Axel Heider made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]
          Jenkins IRC Bot made changes -
          Component/s New: matrix-project [ 18765 ]
          Component/s Original: matrix [ 15501 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 137113 ] New: JNJira + In-Review [ 204381 ]

            kbertelson kbertelson
            axelheider Axel Heider
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: