The blueocean-bitbucket-pipeline plugin still uses “teams” URLs, at least here:

• https://github.com/jenkinsci/blueocean-plugin/blob/239e00a4577564b37ac7bd1b7c90d25a71937c3f/blueocean-bitbucket-pipeline/src/main/java/io/jenkins/blueocean/blueocean_bitbucket_pipeline/cloud/BitbucketCloudApi.java#L105
• https://github.com/jenkinsci/blueocean-plugin/blob/239e00a4577564b37ac7bd1b7c90d25a71937c3f/blueocean-bitbucket-pipeline/src/main/java/io/jenkins/blueocean/blueocean_bitbucket_pipeline/cloud/BitbucketCloudApi.java#L137

So these have to be changed to “workspaces”. Perhaps references to “owner” have to be changed as well.

I don’t intend to work on that.

i tried to reinstall Blue Ocean, but have same issues

http://*MYIP*/blue/rest/organizations/jenkins/scm/bitbucket-cloud/organizations/%**%*D/repositories/?credentialId=bitbucket-cloud&pageNumber=1&pageSize=100&apiUrl=[https://bitbucket.org|https://bitbucket.org/]

jimmy1998, I was hoping to see a Jenkins stack trace. However, it is now clear that the problem is indeed in blueocean-bitbucket-pipeline and has to be fixed there.

So far, I don't see any such fix in https://github.com/jenkinsci/blueocean-plugin/pulls and I don't know whether anybody is working on it. (PR #2196 will not help; it upgrades the build-time cloudbees-bitbucket-branch-source dependency to 2.9.11, but if you have installed that version, then it is used at run time anyway, even without this PR.)

Until there is a fix, you can perhaps work around the issue by using the older Jenkins user interface instead of Blue Ocean.

ok, thanks