Check that both of your personal and work account have the correct public keys added for access. Fixed Optional integration settings not being saved Fixed Launch ssh agent option in Tools not doing any operation Fixed continue interactive rebase failing Fixed custom actions not performing any operation Fixed Sourcetree crashing on chekout/clone from bitbucket Fixed Commit text links not being saved SourceTree 3.4.2 07 January 2021.Save the private and public keys for later use. Fresh Start: If you want to start from scratch, generate two new keys in PuttyGen.rsa to the file name so you can differentiate from your ppk format private key. Existing Keys: If you previously used Putty, load your ppk into PuttyGen and convert it to Open SSH format using the conversion option.We'll be implementing the scenario where you have 1 work and 1 personal Github/Bitbucket/Gitlab account Obviously this is Windows and Git specific. I have recorded the steps I took to guarantee a sure-fire process to achieve functional Windows Sourcetree with Git working on multiple SSH keys. What I found most interesting was that every document explaining how to do this omitted one or two critical details. This week we have officially adopted two-factor authentication for our revision control so guess what?!Īs the documentation clearly states, this breaks HTTPS login for Git!Īll things considered this is a small issue but getting multi-key SSH configured was surprisingly difficult. To avoid SSH key issues we just use simple HTTPS to clone our repos down instead of hassling with multiple SSH keys. Unfortunately, clicking on the 'Remote' button opens up a dead link. We are using/testing BitBucket Server and have it working fine with SourceTree on two separate computers. Sometimes we work from our personal computers and being developers, we have our own projects outside of work that are associated with different credentials. SourceTrees 'Remote' button opens dead link on BitBucket server. Sorry - a lot of questions - thinking that if I can clean everything and set it up with the recommended configuration then it might shake the problem once and for all.We use Git and Sourcetree, primarily on the Windows operating system and love it 99% of the time. I've seen many crashes of a process included with SourceTree called 'askpass.exe' - at times it's been popping up a crash dialog every hour or two throughout the day - is this part of the problem, and is there something about my environment that needs to be addressed to allow it to run successfully? What 3rd-party services or utilities do I need to have configured and running for authentication to be stable under Windows 10? (Is OpenSSH Authentication Agent required? Do I need a specific version of Pageant? Does the version of git I'm using make a difference - should I go with the embedded version or install something else?) What's the recommended way of setting up SourceTree to authenticate with BitBucket? Is it possible that there's configuration stored in git, or some 3rd-party service, or the repos themselves, which also needs resetting? How can I reset SourceTree so that all pre-existing configuration is removed? then it's good for maybe a few hours before needing to repeat the process. Wait for the browser to open and authenticate. Open the Account being used to connect.Ħ. Cancel the password popup (no password works).ģ. The *only* way I've been able to get SourceTree to talk to the server for years is:ġ. Within an hour or two the authenticated status had timed out and I needed to re-auth. Although SourceTree did initially authenticate with BitBucket ok as it was able to list the repositories in my account, the SSH key shows up in the BitBucket configuration page as Last Used: Never, so probably whatever configuration remained from the previous install has been used instead? When I then opened the Authentication options, it still listed all the Accounts which were present in the last install (3.4.9), so it doesn't seem to have been fully reset. In the last case I reinstalled 3.4.10 and set up SSH key authentication during the install process, however: Following the instructions at - the problem remained. Deleting the passwd file - the problem appeared fixed for a few days maybe, but then came back. Upgrading through many different versions and/or betas - problem has remained. I've had a long-running problem with SourceTree in which every time I pull or push with BitBucket I'm required to re-authenticate (I think it arrived around the time that the UI was overhauled to not show repos down the left-hand-side of the default view).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |