Skip to content

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

Closed

Description

@jenkins-infra-bot

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

      
"serverUrl"/>
      

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

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.


Originally reported by fbelzunc, imported from: Select inside invisibleEntry is not being populated by the backend
  • assignee: jtaboada
  • status: Closed
  • priority: Critical
  • component(s): bitbucket-branch-source-plugin, core
  • label(s): 2.263.2-fixed, tables-to-divs-regression
  • resolution: Fixed
  • resolved: 2020-11-18T16:49:34+00:00
  • votes: 0
  • watchers: 4
  • imported: 2025-11-24
Raw content of original issue

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.

environment
Plugin version: 2.94 <br/>
Jenkins Core version &gt;=2.244
1 attachment

Activity

  1. jenkins-infra-bot commented on Nov 4, 2020

    @jenkins-infra-bot
    Author
  2. jenkins-infra-bot commented on Nov 5, 2020

    @jenkins-infra-bot
    Author
    fqueiruga:
    • Original comment link
    • Raw content of original comment:

      Tagging this one as a tables-to-divs regression as it was introduced at the same time the JS compatibility changes were made.

    Tagging this one as a tables-to-divs regression as it was introduced at the same time the JS compatibility changes were made.

  3. jenkins-infra-bot commented on Nov 8, 2020

    @jenkins-infra-bot
    Author
    timja:
    • Original comment link
    • Raw content of original comment:

      can it be reproduced on Jenkins 2.265?

    can it be reproduced on Jenkins 2.265?

  4. jenkins-infra-bot commented on Nov 9, 2020

    @jenkins-infra-bot
    Author
    timja:
    • Original comment link
    • Raw content of original 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.

    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.

  5. jenkins-infra-bot commented on Nov 10, 2020

    @jenkins-infra-bot
    Author
    fbelzunc:
    • Original comment link
    • Raw content of original 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.

    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.

  6. jenkins-infra-bot commented on Nov 10, 2020

    @jenkins-infra-bot
    Author
    timja:
    • Original comment link
    • Raw content of original comment:

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

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

  7. jenkins-infra-bot commented on Nov 16, 2020

    @jenkins-infra-bot
    Author
    timja:
    • Original comment link
    • Raw content of original comment:

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

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

  8. jenkins-infra-bot commented on Nov 17, 2020

    @jenkins-infra-bot
    Author
    fqueiruga:

    Can this be related to https://issues.jenkins.io/browse/JENKINS-64071 ?

  9. jenkins-infra-bot commented on Nov 17, 2020

    @jenkins-infra-bot
    Author
    timja:
    • Original comment link
    • Raw content of original comment:

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

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

  10. jenkins-infra-bot commented on Nov 17, 2020

    @jenkins-infra-bot
    Author
    fqueiruga:
    • Original comment link
    • Raw content of original comment:

      I'll try to look into it 

       

    I'll try to look into it 

     

  11. jenkins-infra-bot commented on Nov 25, 2020

    @jenkins-infra-bot
    Author
    fqueiruga:

    I have created a PR to fix it on #5081 that will work once a new version of bitbucket-branch-source is released.

  12. removed
    bugFor changelog: Minor bug. Will be listed after features
    on Nov 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions