-
Bug
-
Resolution: Fixed
-
Minor
-
CloudBees CI Client Controller v2.401.2.5-rolling
Bitbucket Server Integration v3.3.2
Bitbucket Server v7.17.10
Following the instructions, it says to select HTML Access Token which isn't available in our Bitbucket version and isn't an option in Cloudbees. Selected Personal Access Token in Cloudbees, created one in Bitbucket, and entered in the correct URL for our instance. However, no matter what, the created token name does not appear in the dropdown. I even tried creating a SSH user but that also fails to populate the user in the dropdown. I thought it might have been a UI issue with Chrome but the problem remains in Edge.
Hi Edwin thanks for the report.
To clarify the issue I need more information:
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