-
Bug
-
Resolution: Fixed
-
Highest
-
None
-
2.4
-
Mac OS X Sierra desktop
Bitbucket Server
Sourcetree 2.4 (and the Beta has this problem too)
-
Severity 2 - Major
Please watch my short video illustrating the experience.
https://www.youtube.com/watch?v=wPUAkG78BFE&feature=youtu.be
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.
Please watch my short video illustrating the experience.
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-4446] Generating SSH Keys is broken (using Bitbucket Server) -- ui and config file
Michael S Wilde
added a comment - Thanks for the help Brian... when can/should I test? I think that's everything. Will be available in the next build, likely pushed tomorrow afternoon. Thank you again for the detailed report and video.
Scenario 1:
3. We now create temp accounts as type and configure in welcome wizard; this means new ones can be generated and will be detected properly
Scenario 2:
4. We now create temp accounts for Bitbucket Server as you type; this means new ones can be generated and will be detected properly
Michael S Wilde
added a comment - cool.. looking forward to testing it.. and seeing if using SSH makes any improvement with gitflow (As i've seen some weird problems with it). Either way.. once y'all get that thing released, i'll be doing an internal training video as i encourage people to use as the git cli can't hold a candle to SourceTree
Michael S Wilde
added a comment - cool.. looking forward to testing it.. and seeing if using SSH makes any improvement with gitflow (As i've seen some weird problems with it). Either way.. once y'all get that thing released, i'll be doing an internal training video as i encourage people to use as the git cli can't hold a candle to SourceTree My goal is to ship these in the next build that's pushed to both beta and release channels concurrently before the end of this week.
Michael S Wilde
added a comment - look at you guys.. just hammerin away!!! Thanks.. Does that end up a build, or beta soon? if so, when (i dont know your beta/release drop cycle).
Michael S Wilde
added a comment - look at you guys.. just hammerin away!!! Thanks.. Does that end up a build, or beta soon? if so, when (i dont know your beta/release drop cycle). Scenarios 1 & 2:
2. The password field is now hidden when SSH is the selected protocol.
Scenario 2
5. Public/Private Keys are now generated with an escaped host from the URL (user_your-server-com) and written to the config properly as "HostName your.server.com"
There's no pre-release testing build, it will hit both beta and release channels tomorrow after we wrap up a few other things.