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

Parameterized build can not save the "Parameter Description" in the first time

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • core
    • Jenkins latest version 1.563

      Job -> Configuration -> This build is parameterized -> "add some kind of parameter" -> "enter some description" -> Save

      For this case, we do the 1st "Save" action, it doesn't make sense. the "description" disappear.
      We need to re-configuration for the Job parameter description. Save in 2ed time.

          [JENKINS-23026] Parameterized build can not save the "Parameter Description" in the first time

          Bao Xiaopan(Bob) created issue -

          Daniel Beck added a comment -

          Reducing priority as workaround is easy and obvious, and parameter descriptions are only a UI element.

          Daniel Beck added a comment - Reducing priority as workaround is easy and obvious, and parameter descriptions are only a UI element.
          Daniel Beck made changes -
          Priority Original: Critical [ 2 ] New: Minor [ 4 ]

          Chris Tutty added a comment -

          Seriously Daniel? "...only a UI element"? I use descriptions to comment parameter dependencies and guide input. That's like saying code comments aren't required by the parser so they're not important. Throwing away user input should always be treated as a critical fault, but I'm new here.

          Chris Tutty added a comment - Seriously Daniel? "...only a UI element"? I use descriptions to comment parameter dependencies and guide input. That's like saying code comments aren't required by the parser so they're not important. Throwing away user input should always be treated as a critical fault, but I'm new here.

          Daniel Beck added a comment -

          Yes, I'm serious (I could be wrong though). While there is "loss of data", it's a parameter description, not your released build (or even a script like JENKINS-23151). Let's not overrate it.

          Daniel Beck added a comment - Yes, I'm serious (I could be wrong though). While there is "loss of data", it's a parameter description, not your released build (or even a script like JENKINS-23151 ). Let's not overrate it.
          Daniel Beck made changes -
          Link New: This issue is related to JENKINS-23151 [ JENKINS-23151 ]

          Chris Tutty added a comment -

          I withdraw (after reading the definition of "Major" while posting a related bug which I obviously should have done before commenting). It's the kind of thing that I don't like seeing trivialised, but I think you're correct in assessing it as Minor.

          Chris Tutty added a comment - I withdraw (after reading the definition of "Major" while posting a related bug which I obviously should have done before commenting). It's the kind of thing that I don't like seeing trivialised, but I think you're correct in assessing it as Minor.

          Daniel Beck added a comment -

          As mentioned in the comments to JENKINS-23148, the new CodeMirror also breaks accessibility for blind users.

          Daniel Beck added a comment - As mentioned in the comments to JENKINS-23148 , the new CodeMirror also breaks accessibility for blind users.
          Daniel Beck made changes -
          Link New: This issue is related to JENKINS-23148 [ JENKINS-23148 ]

          Donato Tagliabue added a comment -

          Hi, I've the same problem. The behaviour is the same as in Jenkins-23151 bug. The workaround also in this case is to "apply" the modifications (the new build parameter description) before saving

          Donato Tagliabue added a comment - Hi, I've the same problem. The behaviour is the same as in Jenkins-23151 bug. The workaround also in this case is to "apply" the modifications (the new build parameter description) before saving

            Unassigned Unassigned
            xiaopan3322 Bao Xiaopan(Bob)
            Votes:
            2 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: