Hi Edwin thanks for the report.

To clarify the issue I need more information:

• What kind of credential are you creating? The credential type must be "Bitbucket personal access token"
• What are you trying to attach the personal access token to? You may only use the personal access token credential type when specifying the instance- if you want to attach a token to a job as part of an SCM or SCM source, you must use Username/Password credentials (you can still use an access token, it is entered as the password of that credential type)
• Can you confirm the credential is being created successfully? You can do this by looking at the credentials on the credential page, and verifying in your `credentials.xml` that the type is `com.atlassian.bitbucket.jenkins.internal.config.BitbucketTokenCredentialsImpl`.
• What's the scope of your credential?
• Are you seeing any errors or issues on credential creation or when selecting the dropdown in the jenkins logs?

The list filters out any credentials not matching the "Bitbucket personal access token" type when specifying the access token, which is why some credentials do not appear in that list.

Thanks,

Martin

Thank you for the comments. I will take a look at your questions and reply back though it might be a business day or three.

Greetings! Finally get back to this. So, to hop in:

1) The credential being made is "Bitbucket personal access token".

2) The token I am trying to use is to add our Bitbucket Server instance to the System Configuration.

3) Yes, I see my token sitting in the credentials.xml file. I will say, however, there are multiple Bitbucket tokens in the XML file and even these don't appear in the dropdown. The type is as stated in your question.

4) Scope for mine is SYSTEM.

5) Errors seen include:

but the one that is seen a lot when attempting this is:

So, earlier today (of this post), the Cloudbees admin upgraded to v2.401.3.3-rolling. This, then, allowed us to upgrade the plug-in to v3.5.0. This cured the problem. In fact, all of the credentials listed in the XML files appeared in the dropdown. So, looks like this is resolved!

Cloudbees was upgraded to CI Client Controller v2.401.3.3-rolling which permitted the upgrade of the plug-in to v3.5.0 and the problem was corrected with all token credentials being listed in the dropdown when setting up Bitbucket Server in the System settings.