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

Default value for Build selector parameter is not saved

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Minor Minor
    • promoted-builds-simple-plugin
    • None
    • Jenkins ver. 1.630
      CopyArtifact-plugin ver. 1.36

      To reproduce: For a build parameter of type "Build selector for Copy Artifact" set the default selector to "Last promoted build" and set the "Promotion level" to any level that is not first in the list. Save project. Re-open settings and observe that the promotion level was not saved but it has been reset back to the first value on the list.

          [JENKINS-32052] Default value for Build selector parameter is not saved

          Seth Reno added a comment -

          I'm seeing this also. One small correction to the original issue description... The value is saved when you select it and save the project configuration. I verified this by looking at the value in the config.xml file for the project. However, once you re-open the project configuration page the appropriate value is no longer selected.

          Jenkins 1.641
          Copy Artifact Plugin 1.37

          Seth Reno added a comment - I'm seeing this also. One small correction to the original issue description... The value is saved when you select it and save the project configuration. I verified this by looking at the value in the config.xml file for the project. However, once you re-open the project configuration page the appropriate value is no longer selected. Jenkins 1.641 Copy Artifact Plugin 1.37

          ikedam added a comment -

          This is an issue of promoted-builds-simple plugin.
          See JENKINS-29767 for details.

          ikedam added a comment - This is an issue of promoted-builds-simple plugin. See JENKINS-29767 for details.

            Unassigned Unassigned
            jlehtnie Jukka Lehtniemi
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: