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

          Félix Belzunce Arcos created issue -
          Félix Belzunce Arcos made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Félix Belzunce Arcos made changes -
          Description Original: If under Manage Jenkins -> Configure System -> Bitbucket we ONLY configure a SINGLE BitBucket Server - and we remove the BitBucket Cloud configuration which is by default, thus there is ONLY one server in the list. Then, if we create a multibranch job the dropdown menu which displays ALL the servers does not pop up because there is a single server to be used. However, in the source code we are assuming that in this case ,we will be always reaching https://bitbucket.org instead of the serverUrl we configured under Manage Jenkins -> Configure System -> Bitbucket New:


          If under Manage Jenkins -> Configure System -> Bitbucket we ONLY configure a SINGLE BitBucket Server - and we remove the BitBucket Cloud configuration which is by default, thus there is ONLY one server in the list. Then, if we create a multibranch job the dropdown menu which displays ALL the servers does not pop up because there is a single server to be used. However, in the source code we are assuming that in this case ,we will be always reaching https://bitbucket.org instead of the serverUrl we configured under Manage Jenkins -> Configure System -> Bitbucket
          Félix Belzunce Arcos made changes -
          Environment Original: 2.94 New: 2.94 Jenkins Core version >=2.44
          Félix Belzunce Arcos made changes -
          Environment Original: 2.94 Jenkins Core version >=2.44 New: Plugin version: 2.94
          Jenkins Core version >=2.244
          Félix Belzunce Arcos made changes -
          Description Original:


          If under Manage Jenkins -> Configure System -> Bitbucket we ONLY configure a SINGLE BitBucket Server - and we remove the BitBucket Cloud configuration which is by default, thus there is ONLY one server in the list. Then, if we create a multibranch job the dropdown menu which displays ALL the servers does not pop up because there is a single server to be used. However, in the source code we are assuming that in this case ,we will be always reaching https://bitbucket.org instead of the serverUrl we configured under Manage Jenkins -> Configure System -> Bitbucket
          New: h3. Issue

          h3. Environment

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


          h3. 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.243

          {code:java}
          <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>
          {code}

          * Before 2.244

          {code:java}
          <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>
          {code}

          h3. Impact

          Since 2.244, this plugin will not be able to create new multi-branch or modify the existing ones.



          Félix Belzunce Arcos made changes -
          Description Original: h3. Issue

          h3. Environment

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


          h3. 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.243

          {code:java}
          <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>
          {code}

          * Before 2.244

          {code:java}
          <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>
          {code}

          h3. Impact

          Since 2.244, this plugin will not be able to create new multi-branch or modify the existing ones.



          New: h3. Issue

          A single BitbucketEndpoint configured as BitbucketServerEndpoint tries to authenticate against the Cloud URL

          h3. Environment

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


          h3. 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.243

          {code:java}
          <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>
          {code}

          * Before 2.244

          {code:java}
          <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>
          {code}

          h3. Impact

          Since 2.244, this plugin will not be able to create new multi-branch or modify the existing ones.



          Félix Belzunce Arcos made changes -
          Description Original: h3. Issue

          A single BitbucketEndpoint configured as BitbucketServerEndpoint tries to authenticate against the Cloud URL

          h3. Environment

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


          h3. 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.243

          {code:java}
          <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>
          {code}

          * Before 2.244

          {code:java}
          <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>
          {code}

          h3. Impact

          Since 2.244, this plugin will not be able to create new multi-branch or modify the existing ones.



          New: h3. Issue

          A single BitbucketEndpoint configured as BitbucketServerEndpoint tries to authenticate against the Cloud URL

          *This is also*

          h3. Environment

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


          h3. 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.243

          {code:java}
          <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>
          {code}

          * Before 2.244

          {code:java}
          <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>
          {code}

          h3. Impact

          Since 2.244, this plugin will not be able to create new multi-branch or modify the existing ones.



          Félix Belzunce Arcos made changes -
          Component/s New: core [ 15593 ]
          Félix Belzunce Arcos made changes -
          Description Original: h3. Issue

          A single BitbucketEndpoint configured as BitbucketServerEndpoint tries to authenticate against the Cloud URL

          *This is also*

          h3. Environment

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


          h3. 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.243

          {code:java}
          <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>
          {code}

          * Before 2.244

          {code:java}
          <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>
          {code}

          h3. Impact

          Since 2.244, this plugin will not be able to create new multi-branch or modify the existing ones.



          New: h3. Issue

          I can reproduce this issue with the A single BitbucketEndpoint configured as BitbucketServerEndpoint tries to authenticate against the Cloud URL

          *This is mainly a core issue and is *

          h3. Environment

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


          h3. 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.243

          {code:java}
          <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>
          {code}

          * Before 2.244

          {code:java}
          <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>
          {code}

          h3. Impact

          Since 2.244, this plugin will not be able to create new multi-branch or modify the existing ones.



            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: