bitbucket-branch-source-plugin: Unable to create new multibranch pipeline project (Error while loading repositories from cache)

I confirm the bug. My setup is:

• Jenkins: 2.255-1.1.noarch (CentOS Linux release 7.8.2003 (Core))
• Bitbucket Plugin: 1.1.24
• Bitbucket Branch Source Plugin: 2.9.2
• Bitbucket Server: v6.10.0

@hoffmale , your fix works fine

Manually exchanging the serverUrl in a job’s config.xml works, as does copying an already existing job.

Enough to replace https://bitbucket.org to your own bitbucket server URL in config.xml and then do the reread Jenkins config from the Jenkins settings.

I have this problem too

Jenkins 2.253 Bitbucket Branch Source Plugin: 2.9.2 Bitbucket v7.1.3

When I try to create a new multibranch pipeline project, I have the following error:

Could not find: <project_key>

I got over this problem, adding the Bitbucket Cloud endpoint in Jenkins > Config

And, next when I try to create a new project, the repositories are returned correctly, when I select our Bitbucket Server.

Strangely, if I add two servers (prod / dev), without the Bitbucket Cloud server, the problem is also got over.

Same problem here, running Jenkins 2.249.2 and 2.9.4 with a single bitbucket server instance

@rbywater Thank you so much for the code.

@bitwiseman Now is it possible to quickly fix this and release a new version? It should hardly take an hour.

Same issue here. Setting up a new Jenkins Server with OnPremise Bitbucket server.

Used versions:

• Jenkins: 2.249.2
• Bitbucket: 6.10.0
• Bitbucket Branch Source Plugin: 2.9.4

Initial setup:

• Deleted “Bitbucket Cloud”
• Added “Bitbucket Server”
• Provided correct “Server URL”
• Created Multibranch Pipeline Job
• Error Message: “Error while loading repositories from cache”

Solution:

• Added “Bitbucket Cloud” entry again, no further changes
• Selected correct “Bitbucket Server” in Multibranch Pipeline Job
• Repositories can be resolved successfully

I have the same issue and went through the code and couldn’t find anything obvious as to why its stopped working - I can only assume it may be related to a Jenkins core change along the way as well?

I think the fix is to change the line in doFillRepositoryItems serverUrl = StringUtils.defaultIfBlank(serverUrl, BitbucketCloudEndpoint.SERVER_URL); to something like serverUrl = StringUtils.defaultIfBlank(serverUrl, BitbucketEndpointConfiguration.get().getEndpointItems().size() > 0 ? BitbucketEndpointConfiguration.get().getEndpointItems().get(0) : BitbucketCloudEndpoint.SERVER_URL);

(That is if we don’t have a server URL then there’s either 0 or 1 entries, therefore try and see if there is 1 entry and use that, else fall back to using Cloud)

Note the above snippet is completely untested at the mo 😄

@bitwiseman this is the “Bitbucket Integration Plugin”. I set up the connection in the “Bitbucket Integration Plugin” section of the Jenkins config. And this is what works together with the “Bitbucket Branch Source Plugin” at last this is what Jenkins says. Apart from this…it is really annoying that all parties point to each other and the end user has to fiddle around with all this stuff to get it working. As a plugin developer you’re supposed to either deprecate the whole thing and say sorry guys I don't care anymore, bye or fix the damn issue. That’s why in Microsoft Windows there was a fix for Sim City so that the end user (us) doesn’t have to bother. This whole ecosystem is oozing with this shit and I think I should just drop Jenkins and Bitbucket altogether and use an integrated solution that just works. In fact, I just decided to do so now.

Freshly created config.xml:

<?xml version='1.1' encoding='UTF-8'?>
<org.jenkinsci.plugins.workflow.multibranch.WorkflowMultiBranchProject plugin="workflow-multibranch@2.21">
  <actions/>
  <description></description>
  <properties>
    <org.jenkinsci.plugins.docker.workflow.declarative.FolderConfig plugin="docker-workflow@1.23">
      <dockerLabel></dockerLabel>
      <registry plugin="docker-commons@1.17"/>
    </org.jenkinsci.plugins.docker.workflow.declarative.FolderConfig>
  </properties>
  <folderViews class="jenkins.branch.MultiBranchProjectViewHolder" plugin="branch-api@2.5.8">
    <owner class="org.jenkinsci.plugins.workflow.multibranch.WorkflowMultiBranchProject" reference="../.."/>
  </folderViews>
  <healthMetrics>
    <com.cloudbees.hudson.plugins.folder.health.WorstChildHealthMetric plugin="cloudbees-folder@6.14">
      <nonRecursive>false</nonRecursive>
    </com.cloudbees.hudson.plugins.folder.health.WorstChildHealthMetric>
  </healthMetrics>
  <icon class="jenkins.branch.MetadataActionFolderIcon" plugin="branch-api@2.5.8">
    <owner class="org.jenkinsci.plugins.workflow.multibranch.WorkflowMultiBranchProject" reference="../.."/>
  </icon>
  <orphanedItemStrategy class="com.cloudbees.hudson.plugins.folder.computed.DefaultOrphanedItemStrategy" plugin="cloudbees-folder@6.14">
    <pruneDeadBranches>true</pruneDeadBranches>
    <daysToKeep>-1</daysToKeep>
    <numToKeep>-1</numToKeep>
  </orphanedItemStrategy>
  <triggers/>
  <disabled>false</disabled>
  <sources class="jenkins.branch.MultiBranchProject$BranchSourceList" plugin="branch-api@2.5.8">
    <data>
      <jenkins.branch.BranchSource>
        <source class="com.cloudbees.jenkins.plugins.bitbucket.BitbucketSCMSource" plugin="cloudbees-bitbucket-branch-source@2.9.1">
          <id>76c9717a-4416-40a1-a63e-e57fdbb1b45f</id>
          <serverUrl>https://bitbucket.org</serverUrl>
          <credentialsId>sanitized</credentialsId>
          <repoOwner>sanitized</repoOwner>
          <repository></repository>
          <traits>
            <com.cloudbees.jenkins.plugins.bitbucket.BranchDiscoveryTrait>
              <strategyId>1</strategyId>
            </com.cloudbees.jenkins.plugins.bitbucket.BranchDiscoveryTrait>
            <com.cloudbees.jenkins.plugins.bitbucket.OriginPullRequestDiscoveryTrait>
              <strategyId>1</strategyId>
            </com.cloudbees.jenkins.plugins.bitbucket.OriginPullRequestDiscoveryTrait>
          </traits>
        </source>
        <strategy class="jenkins.branch.DefaultBranchPropertyStrategy">
          <properties class="empty-list"/>
        </strategy>
      </jenkins.branch.BranchSource>
    </data>
    <owner class="org.jenkinsci.plugins.workflow.multibranch.WorkflowMultiBranchProject" reference="../.."/>
  </sources>
  <factory class="org.jenkinsci.plugins.workflow.multibranch.WorkflowBranchProjectFactory">
    <owner class="org.jenkinsci.plugins.workflow.multibranch.WorkflowMultiBranchProject" reference="../.."/>
    <scriptPath>Jenkinsfile</scriptPath>
  </factory>
</org.jenkinsci.plugins.workflow.multibranch.WorkflowMultiBranchProject>

Old multibranch pipeline job:

<?xml version='1.1' encoding='UTF-8'?>
<org.jenkinsci.plugins.workflow.multibranch.WorkflowMultiBranchProject plugin="workflow-multibranch@2.21">
  <actions/>
  <description></description>
  <properties>
    <org.jenkinsci.plugins.docker.workflow.declarative.FolderConfig plugin="docker-workflow@1.23">
      <dockerLabel></dockerLabel>
      <registry plugin="docker-commons@1.17"/>
    </org.jenkinsci.plugins.docker.workflow.declarative.FolderConfig>
  </properties>
  <folderViews class="jenkins.branch.MultiBranchProjectViewHolder" plugin="branch-api@2.5.8">
    <owner class="org.jenkinsci.plugins.workflow.multibranch.WorkflowMultiBranchProject" reference="../.."/>
  </folderViews>
  <healthMetrics>
    <jenkins.branch.PrimaryBranchHealthMetric plugin="branch-api@2.5.8"/>
  </healthMetrics>
  <icon class="jenkins.branch.MetadataActionFolderIcon" plugin="branch-api@2.5.8">
    <owner class="org.jenkinsci.plugins.workflow.multibranch.WorkflowMultiBranchProject" reference="../.."/>
  </icon>
  <orphanedItemStrategy class="com.cloudbees.hudson.plugins.folder.computed.DefaultOrphanedItemStrategy" plugin="cloudbees-folder@6.14">
    <pruneDeadBranches>true</pruneDeadBranches>
    <daysToKeep>-1</daysToKeep>
    <numToKeep>-1</numToKeep>
  </orphanedItemStrategy>
  <triggers>
    <com.igalg.jenkins.plugins.mswt.trigger.ComputedFolderWebHookTrigger plugin="multibranch-scan-webhook-trigger@1.0.5">
      <spec></spec>
      <token>B4XiS4FCmzwTZJo7QnW3</token>
    </com.igalg.jenkins.plugins.mswt.trigger.ComputedFolderWebHookTrigger>
  </triggers>
  <disabled>false</disabled>
  <sources class="jenkins.branch.MultiBranchProject$BranchSourceList" plugin="branch-api@2.5.8">
    <data>
      <jenkins.branch.BranchSource>
        <source class="com.cloudbees.jenkins.plugins.bitbucket.BitbucketSCMSource" plugin="cloudbees-bitbucket-branch-source@2.9.1">
          <id>0083f822-4925-4bbc-b831-8f3d001a0e6c</id>
          <serverUrl>sanitized correct URL</serverUrl>
          <credentialsId>sanitized</credentialsId>
          <repoOwner>sanitizied</repoOwner>
          <repository>sanitized</repository>
          <traits>
            <com.cloudbees.jenkins.plugins.bitbucket.BranchDiscoveryTrait>
              <strategyId>1</strategyId>
            </com.cloudbees.jenkins.plugins.bitbucket.BranchDiscoveryTrait>
            <com.cloudbees.jenkins.plugins.bitbucket.OriginPullRequestDiscoveryTrait>
              <strategyId>1</strategyId>
            </com.cloudbees.jenkins.plugins.bitbucket.OriginPullRequestDiscoveryTrait>
          </traits>
        </source>
        <strategy class="jenkins.branch.DefaultBranchPropertyStrategy">
          <properties class="empty-list"/>
        </strategy>
      </jenkins.branch.BranchSource>
    </data>
    <owner class="org.jenkinsci.plugins.workflow.multibranch.WorkflowMultiBranchProject" reference="../.."/>
  </sources>
  <factory class="org.jenkinsci.plugins.workflow.multibranch.WorkflowBranchProjectFactory">
    <owner class="org.jenkinsci.plugins.workflow.multibranch.WorkflowMultiBranchProject" reference="../.."/>
    <scriptPath>Jenkinsfile</scriptPath>
  </factory>
</org.jenkinsci.plugins.workflow.multibranch.WorkflowMultiBranchProject>

Most interesting are the following two snippets (commented): new:

        <source class="com.cloudbees.jenkins.plugins.bitbucket.BitbucketSCMSource" plugin="cloudbees-bitbucket-branch-source@2.9.1">
          <id>76c9717a-4416-40a1-a63e-e57fdbb1b45f</id>
          <serverUrl>https://bitbucket.org</serverUrl> <!-- wrong URL, not the one setup in global settings -->
          <credentialsId>sanitized</credentialsId> <!-- correct credentials -->
          <repoOwner>sanitized</repoOwner> <!-- can still be entered -->
          <repository></repository> <!-- empty in original, failure to load list and then unable to select repository, as described -->
          <traits>
            <com.cloudbees.jenkins.plugins.bitbucket.BranchDiscoveryTrait>
              <strategyId>1</strategyId>
            </com.cloudbees.jenkins.plugins.bitbucket.BranchDiscoveryTrait>
            <com.cloudbees.jenkins.plugins.bitbucket.OriginPullRequestDiscoveryTrait>
              <strategyId>1</strategyId>
            </com.cloudbees.jenkins.plugins.bitbucket.OriginPullRequestDiscoveryTrait>
          </traits>
        </source>

old:

        <source class="com.cloudbees.jenkins.plugins.bitbucket.BitbucketSCMSource" plugin="cloudbees-bitbucket-branch-source@2.9.1">
          <id>0083f822-4925-4bbc-b831-8f3d001a0e6c</id>
          <serverUrl>sanitized correct URL</serverUrl> <!-- correct URL, matches global settings -->
          <credentialsId>sanitized</credentialsId>
          <repoOwner>sanitizied</repoOwner>
          <repository>sanitized</repository> <!-- repo selection works fine -->
          <traits>
            <com.cloudbees.jenkins.plugins.bitbucket.BranchDiscoveryTrait>
              <strategyId>1</strategyId>
            </com.cloudbees.jenkins.plugins.bitbucket.BranchDiscoveryTrait>
            <com.cloudbees.jenkins.plugins.bitbucket.OriginPullRequestDiscoveryTrait>
              <strategyId>1</strategyId>
            </com.cloudbees.jenkins.plugins.bitbucket.OriginPullRequestDiscoveryTrait>
          </traits>
        </source>

For comparison, the global settings look like this:

<?xml version='1.1' encoding='UTF-8'?>
<com.cloudbees.jenkins.plugins.bitbucket.endpoints.BitbucketEndpointConfiguration plugin="cloudbees-bitbucket-branch-source@2.9.1">
  <endpoints>
    <com.cloudbees.jenkins.plugins.bitbucket.endpoints.BitbucketServerEndpoint>
      <manageHooks>false</manageHooks>
      <displayName>sanitized</displayName>
      <serverUrl>sanitized</serverUrl>
      <webhookImplementation>PLUGIN</webhookImplementation>
      <serverVersion>VERSION_6</serverVersion>
      <callCanMerge>true</callCanMerge>
      <callChanges>false</callChanges>
    </com.cloudbees.jenkins.plugins.bitbucket.endpoints.BitbucketServerEndpoint>
  </endpoints>
</com.cloudbees.jenkins.plugins.bitbucket.endpoints.BitbucketEndpointConfiguration>

Manually exchanging the <serverUrl> in a job’s config.xml works, as does copying an already existing job. I have no idea where the https://bitbucket.org server URL comes from; my assumption is that this is the bitbucket cloud one?

Adding a second (dummy) Bitbucket Server entry worked fine for me, as a workaround. Damyan

Hello,

have same issue. I don’t use bitbucket cloud and now configuring a job with only one server configured in Jenkins makes the plugin try to call “ghost cloud” account instead of using the only one declared in the server settings.

Adding two servers or one cloud and one on premise in the config, makes the “list box model” appearing in the Multibranch job source and you can then select which server to use and it’s fine.

This is my init groovy script and I had to explicitly remove the default “bitbucket cloud” instance having to remove all endpoints and adding the only one I need.

bitbucketEndpoint.getEndpoints().each { bitbucketEndpoint.removeEndpoint(it) }

#!groovy

// imports
import com.cloudbees.plugins.credentials.*
import com.cloudbees.plugins.credentials.impl.*
import jenkins.model.Jenkins
import com.cloudbees.jenkins.plugins.bitbucket.endpoints.*
import com.cloudbees.jenkins.plugins.bitbucket.server.BitbucketServerVersion;

def YELLOW = '\u001B[33m'

def bitbucketEndpointParameters = [
    displayName: 'xxx-Bitbucket' ,
    serverUrl: 'https://git.xxxxx.com',
    manageHooks:   false,
    credentialsId: 'git-reader',
    callCanMerge: false,
    callChanges: false,
    serverVersion: BitbucketServerVersion.VERSION_6
]

// get Jenkins instance
Jenkins jenkins = Jenkins.getInstance()

// get Bitbucket endpoint configuration
def bitbucketEndpoint = jenkins.getDescriptor("com.cloudbees.jenkins.plugins.bitbucket.endpoints.BitbucketEndpointConfiguration")

// define Bitbucket server endpoint
def BitbucketServerEndpoint = new BitbucketServerEndpoint(
    bitbucketEndpointParameters.displayName,
    bitbucketEndpointParameters.serverUrl,
    bitbucketEndpointParameters.manageHooks,
    bitbucketEndpointParameters.credentialsId
)

// only available on bitbucket v7+
BitbucketServerEndpoint.setCallCanMerge(bitbucketEndpointParameters.callCanMerge)
BitbucketServerEndpoint.setCallChanges(bitbucketEndpointParameters.callChanges)
BitbucketServerEndpoint.setServerVersion(bitbucketEndpointParameters.serverVersion)

//Remove all endpoints. If someone added new one using UI all should be wiped out
//Default add empty bitbucket cloud endpoint for no reason....
bitbucketEndpoint.getEndpoints().each {
  bitbucketEndpoint.removeEndpoint(it)
}

def List<AbstractBitbucketEndpoint> listBitbucketServerEndpoint = [BitbucketServerEndpoint]
// set endpoints
bitbucketEndpoint.setEndpoints(listBitbucketServerEndpoint)

// save to disk
jenkins.save()

println("${YELLOW}Configuring Bitbucket branch sources plugin done")