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

Extended Choice Parameter - Parsing values different for on demand builds and builds started by timer

    Details

    • Similar Issues:

      Description

      I am observing different behaviours of the plugin when triggering the build manually and when the build is triggered by the timer. The field is configured this way:

      • Parameter type: check boxes
      • Delimiter: (a space)
      • Source for Value: Value = -p,-t,-v
      • Default Value: Value = -p, -t
      • If I run a build manually (leaving the defaults) to print the value of the variable which holds the param the output is:
        + echo -p -t
        -p -t
        
      • If I the build runs with a timer the output is:
        + echo -p, -t
        -p, -t
        

      I've tried the following configuration, which works as expected, however, the default options are not marked when clicking Build with parameters

      • Parameter type: check boxes
      • Delimiter: (a space)
      • Source for Value: Value = -p,-t,-v
      • Default Value: Value = -p -t

        Attachments

          Activity

          Hide
          andr00 andr00 added a comment -

          I see similiar behavior on Jenkins 1.628, Extended-Choice Parameter Plugin 0.48, OSX 10.10:
          Observed:
          On a manually triggered build, the comma-separated defaults are parsed and applied to the settings checkboxes, then those are joined with the custom delimiter (a semicolon in my case) and passed to the build.

          On a timer or SCM triggered build, any build that does not involve the user confirming the settings, the literal, comma-separated default string is passed to the build.

          Expected: On an automatically triggered build, the default string should be separated on commas and then joined by the custom delimiter before passing to the build.

          Show
          andr00 andr00 added a comment - I see similiar behavior on Jenkins 1.628, Extended-Choice Parameter Plugin 0.48, OSX 10.10: Observed : On a manually triggered build, the comma-separated defaults are parsed and applied to the settings checkboxes, then those are joined with the custom delimiter (a semicolon in my case) and passed to the build. On a timer or SCM triggered build, any build that does not involve the user confirming the settings, the literal, comma-separated default string is passed to the build. Expected : On an automatically triggered build, the default string should be separated on commas and then joined by the custom delimiter before passing to the build.
          Hide
          sdalex Alexandre Martel added a comment -

          Same problem happen with Jenkins ver. 2.106, Extended-Choice Parameter plugin 0.76

          The character delimiter ; is replace with , when the build is automatically triggered by a timer.

          Show
          sdalex Alexandre Martel added a comment - Same problem happen with Jenkins ver. 2.106, Extended-Choice Parameter plugin 0.76 The character delimiter ; is replace with , when the build is automatically triggered by a timer.

            People

            • Assignee:
              vimil vimil
              Reporter:
              david_rubio David Rubio
            • Votes:
              4 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated: