High Summary
The clone URL is empty (blank) when the following conditions are met:
- no ssh key is available for the user, therefore SSH is not available as a clone protocol
- a mirror URL is selected
Steps to Reproduce
- Setup a user with no ssh key
- Setup a mirror
- Attempt to perform a clone and switch to one of the available mirrors from the "Clone from" drop down
Expected Results
The clone URL is prefilled.
Actual Results
The clone URL is empty.
Notes
Switching to a different mirror or to the upstream server will not populate the clone URL.
To obtain the upstream server URL, select "Primary server" from the "Clone from" drop down and refresh the page.
Workaround
The following alternatives can be used:
- manually retrieve the mirror URL
- add an SSH key to the user
- is caused by
-
BSERV-7248 Update the label of the clone dropdown to show HTTPS when in use
- Gathering Interest
- mentioned in
-
![[Extranet] Page](/images/icons/generic_link_16.png "[Extranet] Page")
Page
Failed to load
[BSERV-10478] Clone URL is empty when no ssh key is available for the user and a mirror URL is selected
John Gnagy
added a comment - FYI, this bug is delaying our switch to the data center edition of bitbucket. We have hundreds of users who do not use ssh keys today, and asking windows users who may not be familiar with ssh to generate keys and add them to Bitbucket is a cumbersome workaround at best. Asking them to manually construct a clone URL when they don't know the semantics of the mirror URL paths is not a workaround at all. This bug essentially means we cannot ask our organization to use mirrors, which is the primary driver for switching to the data center edition for us. Hopefully it is an easy bug to fix, but the "low" priority currently assigned to it doesn't give a lot of confidence that it will be fixed soon.
John Gnagy
added a comment - FYI, this bug is delaying our switch to the data center edition of bitbucket. We have hundreds of users who do not use ssh keys today, and asking windows users who may not be familiar with ssh to generate keys and add them to Bitbucket is a cumbersome workaround at best. Asking them to manually construct a clone URL when they don't know the semantics of the mirror URL paths is not a workaround at all. This bug essentially means we cannot ask our organization to use mirrors, which is the primary driver for switching to the data center edition for us. Hopefully it is an easy bug to fix, but the "low" priority currently assigned to it doesn't give a lot of confidence that it will be fixed soon.
This issue has been fixed in release 5.7.0