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

Credentials Binding step repeatable property uses non-unique ID

    • 2.400

      Similar to the fix for JENKINS-70139 to have booleanRadio use non-unique IDs in core Jenkins, the repeatableHeteroProperty construct has generated IDs, so when you have a repeatable describable (e.g. Credentials Binding step) then this ID will be duplicated for all instances.

      Credentials Binding plugin example - you can see in the repeating Username and password (separated) sections only one radio button can be selected / active. This is more than just visual, the values are not enabled.

      https://github.com/jenkinsci/credentials-binding-plugin/blob/master/src/main/resources/org/jenkinsci/plugins/credentialsbinding/impl/BindingStep/config.jelly#L34

          [JENKINS-70988] Credentials Binding step repeatable property uses non-unique ID

          Tom added a comment -

          This is preventing us from upgrading beyond Jenkins 2.391

          Tom added a comment - This is preventing us from upgrading beyond Jenkins 2.391

          james added a comment -

          We are seeing this on the FreeStyle Project config page when doing bindings as well. It started at 2.391 and continues through 2.397 which is the last version we have tested for this. 

          james added a comment - We are seeing this on the FreeStyle Project config page when doing bindings as well. It started at 2.391 and continues through 2.397 which is the last version we have tested for this. 

          Jesse Glick added a comment -

          I suspect the problem lies not in the credentials-binding plugin itself, but in these low-level form controls in the credentials plugin.

          Jesse Glick added a comment - I suspect the problem lies not in the credentials-binding plugin itself, but in these low-level form controls in the credentials plugin.

          Jesse Glick added a comment -

          (Should really be marked “fixed but unreleased”.)

          Jesse Glick added a comment - (Should really be marked “fixed but unreleased”.)

          Tom added a comment -

          Do we have an anticipated release version / date?

          Tom added a comment - Do we have an anticipated release version / date?

          Mark Waite added a comment -

          Tomorrow's weekly release 2.400 will include the fix.

          Mark Waite added a comment - Tomorrow's weekly release 2.400 will include the fix.

            jglick Jesse Glick
            tbeukhof Tom
            Votes:
            1 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: