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

Select inside invisibleEntry is not being populated by the backend

      Issue

      I can reproduce this issue with the bitbucket-branch-source-plugin, in which a single BitbucketEndpoint configured as BitbucketServerEndpoint tries to authenticate against the Cloud URL instead of the Server URL.

      The problem comes when you have something like this in the jelly - but maybe there are more use cases

            <f:invisibleEntry>
              <f:select field="serverUrl"/>
            </f:invisibleEntry>
      

      Not sure if this also happens for other like f:textbox, ... Something to be investigated.

      Environment

      The following issue happens specifically when Jenkins Core version is >= 2.244. Before this version, the issue is not reproducible.

      Reproduction steps

      To reproduce the issue:

      0. Environment: In order to reproduce this issue, you need a Bitbucket Server up and running.
      1. Under Manage Jenkins -> Configure System -> Bitbucket ONLY configure a SINGLE BitBucket Server (it can't be the CLOUD one, we need the Server option)
      2. Now, create a multibranch job. Then, the dropdown menu which displays ALL the servers does not pop up because there is a single server to be used. The plugin is not able to recognize any repository under the ListBox "Repository Name" once owner is filled-up.

      From what I can see using the Developer Console of the Webbrowser, before 2.244 the options are pushed by the backend, but after this version this is not happening anymore.

      • After >= 2.244
      <select fillurl="/jenkins/job/multibranch-a/descriptorByName/com.cloudbees.jenkins.plugins.bitbucket.BitbucketSCMSource/fillRepositoryItems" filldependson="serverUrl credentialsId repoOwner" name="_.repository" class="setting-input  select" value=""></select>
      
      • Before < 2.244
      <select fillurl="/jenkins/job/multibranch-a/descriptorByName/com.cloudbees.jenkins.plugins.bitbucket.BitbucketSCMSource/fillRepositoryItems" filldependson="serverUrl credentialsId repoOwner" name="_.repository" class="setting-input  select" value=""><option value="test-1">test-1</option><option value="test-fbelzunc">test-fbelzunc</option></select>
      

      Impact

      Since 2.244, all select (and perhaps other types) under f:invisibleEntry will not be populated by the backend. All plugins using this approach are susceptible to stop working properly.

          [JENKINS-64125] Select inside invisibleEntry is not being populated by the backend

          Tim Jacomb added a comment -

          can it be reproduced on Jenkins 2.265?

          Tim Jacomb added a comment - can it be reproduced on Jenkins 2.265?

          Tim Jacomb added a comment -

          is this still reproducible?

          and is there a simpler case? having to start up bitbucket server and figure out how to configure it is a high barrier to entry to look at this.

          Tim Jacomb added a comment - is this still reproducible? and is there a simpler case? having to start up bitbucket server and figure out how to configure it is a high barrier to entry to look at this.

          timja Yes, I can always reproduce this issue. I just checked in 2.265 and the behavior seems to be worse, I can't add the Bitbucket as Branch Source. I am using 2.9.4 of the bitbucket-branch-source plugin. The issue is easily reproducible.

          Félix Belzunce Arcos added a comment - timja Yes, I can always reproduce this issue. I just checked in 2.265 and the behavior seems to be worse, I can't add the Bitbucket as Branch Source. I am using 2.9.4 of the bitbucket-branch-source plugin. The issue is easily reproducible.

          Tim Jacomb added a comment -

          New version of branch api and folder plugin are released now which should fix that issue

          Tim Jacomb added a comment - New version of branch api and folder plugin are released now which should fix that issue

          Tim Jacomb added a comment -

          fbelzunc can you reproduce this on 2.266 and latest branch api / folder plugins?

          Tim Jacomb added a comment - fbelzunc can you reproduce this on 2.266 and latest branch api / folder plugins?

          Félix Queiruga Balado added a comment - Can this be related to https://issues.jenkins.io/browse/JENKINS-64071  ?

          Tim Jacomb added a comment -

          Possibly, which is why I asked if it could be re-produced any more

          Tim Jacomb added a comment - Possibly, which is why I asked if it could be re-produced any more

          I'll try to look into it 

           

          Félix Queiruga Balado added a comment - I'll try to look into it   

          I have created a PR to fix it on https://github.com/jenkinsci/jenkins/pull/5081 that will work once a new version of bitbucket-branch-source is released.

          Félix Queiruga Balado added a comment - I have created a PR to fix it on https://github.com/jenkinsci/jenkins/pull/5081  that will work once a new version of bitbucket-branch-source is released.

          Liam Newman added a comment - https://github.com/jenkinsci/bitbucket-branch-source-plugin/releases/tag/cloudbees-bitbucket-branch-source-2.9.5

            jtaboada Jose Blas Camacho Taboada
            fbelzunc Félix Belzunce Arcos
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: