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.