• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • core
    • 2.428, 2.426.1

      Since https://github.com/jenkinsci/jenkins/pull/7658 JENKINS-70729

      clouds are managed via a separate page instead of a list of descriptors. The previous configuration allowed reordering clouds, which affects the node provisioning.

      The new UX doesn't allow that anymore. Some controls should be added to allow reordering, or a specific page.

          [JENKINS-72020] Unable to reorder clouds anymore via UI

          Vincent Latombe created issue -
          Vincent Latombe made changes -
          Link New: This issue is caused by JENKINS-70729 [ JENKINS-70729 ]
          Vincent Latombe made changes -
          Summary Original: Unable to reorder clouds New: Unable to reorder clouds anymore via UI
          Vincent Latombe made changes -
          Description Original: Since https://github.com/jenkinsci/jenkins/pull/7658 JENKINS-70729

          clouds are managed via a separate page instead of a list of descriptors. The previous configuration allowed reordering clouds, which affects the node provisioning.

          The new UX doesn't allow that anymore. Some controls should be added to allow reordering.
          New: Since https://github.com/jenkinsci/jenkins/pull/7658 JENKINS-70729

          clouds are managed via a separate page instead of a list of descriptors. The previous configuration allowed reordering clouds, which affects the node provisioning.

          The new UX doesn't allow that anymore. Some controls should be added to allow reordering, or a specific page.
          Vincent Latombe made changes -
          Remote Link New: This issue links to "PR #8492 (Web Link)" [ 28940 ]
          Alexander Brandes made changes -
          Released As New: 2.428
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Closed [ 6 ]

          Mark Waite added a comment -

          vlatombe this issue is not marked as an LTS candidate currently but it would be eligible for a backport to Jenkins 2.426.1. Do you feel that it should be backported into the 2.426.1 release or is it better to wait for 2.426.2 or even the next LTS baseline?

          Mark Waite added a comment - vlatombe this issue is not marked as an LTS candidate currently but it would be eligible for a backport to Jenkins 2.426.1. Do you feel that it should be backported into the 2.426.1 release or is it better to wait for 2.426.2 or even the next LTS baseline?
          Tim Jacomb made changes -
          Labels New: lts-candidate
          Mark Waite made changes -
          Labels Original: lts-candidate New: 2.426.1-fixed
          Mark Waite made changes -
          Released As Original: 2.428 New: 2.428, 2.426.1

            Unassigned Unassigned
            vlatombe Vincent Latombe
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: