- Status:Closed(View Workflow)
- Resolution: Duplicate
- Fix Version/s: None
- Labels:
- Environment:Mac OS X Sierra desktopBitbucket ServerSourcetree 2.4 (and the Beta has this problem too)
After putting my public key in my account on Bitbucket and trying to clone, errors are related to what is in the '.ssh/config' file this occurs. No hostname is in the '.ssh/config' file (edited by SourceTree) causing a failure on clone When hostname is added, errors occur due to 'space' in filename. See Access keys for details on how to add a public key to a Bitbucket repo. Use multiple SSH keys in your pipeline. Bitbucket Pipelines supports one SSH key per repository. However, you can use multiple keys with a pipeline by adding them as secured variable s, and referencing them in the bitbucket-pipelines.yml file.
Please watch my short video illustrating the experience. Cuphead steam key generator no human verification 2020.
https://www.youtube.com/watch?v=wPUAkG78BFE&feature=youtu.be
https://www.youtube.com/watch?v=wPUAkG78BFE&feature=youtu.be
Generating Ssh Key For Bitbucket
Scenario 1:
On MacOS X Sierra when setting up SourceTree for first time and choosing 'SSH' as the authentication method, SourceTree:
- Should not have a URL for the Bitbucket server, should be a hostname without the https://
- Should not need a 'password'
- Generate SSH Key button is greyed out
- User can skip setup and perform this step manually through the Remote Repository Browser's 'Add Account' function
Scenario 2
On MacOS X Sierra when using the 'Add Account' function the experience when selecting SSH as the authentication method is:
- URL is asked for, should be a hostname
- Password is not needed
- User should be able to select an existing ssh key on their system
- Generate Key button is visible and clickable, when clicked, process continues, but no key is generated and a 'Tooltip' is displayed when account is saved indicating no SSH key
- When editing the account, and selecting 'Generate Key' it now works (but generates a public/private key with a 'space' in the filename (e.g. mwilde_Bitbucket Server.pub)
After putting my public key in my account on Bitbucket and trying to clone, errors are related to what is in the '.ssh/config' file this occurs.
- No hostname is in the '.ssh/config' file (edited by SourceTree) causing a failure on clone
- When hostname is added, errors occur due to 'space' in filename
- When '.ssh/config' is edited removing spaces and subsequently renaming the private key to match the reference in the '.ssh/config' file
After 'fixing' all of these issues, cloning only works thru the CLI, or via a 'Clone in SourceTree' link up in Bitbucket Server. Cloning does not work through the remote repository browser.
![Generating Ssh Keys For Bitbucket Generating Ssh Keys For Bitbucket](/uploads/1/2/5/8/125876498/745215027.png)
![Keys Keys](/uploads/1/2/5/8/125876498/663125815.png)
Please watch my short video illustrating the experience.
https://www.youtube.com/watch?v=wPUAkG78BFE&feature=youtu.be
https://www.youtube.com/watch?v=wPUAkG78BFE&feature=youtu.be
Note: I have a few hundred people in my company i'd like to train on SourceTree (and have them use SSH keys if possible), so please fix this ASAP.
SRCTREE-4500Generating SSH Keys is broken (using Bitbucket Server) -- ui and config file
- Closed
SRCTREE-4505Generating SSH Keys is broken (using Bitbucket Server) -- ui and config file
- Closed
- Assignee:
- Brian Ganninger (Inactive)
- Reporter:
- jamie goodwin
- Votes:
- 0Vote for this issue
- Watchers:
- 1Start watching this issue