If you have installed Git using msysGit on Windows (explained in part1 of my blog series and this step-by-step-addon), then you’ll have “ GitBash“.
(If someone knows better or easier ways to use ssh with Git and Mercurial on Windows, feel free to comment) Unfortunately ssh on Windows isn’t so easy – I read many blogs and here are my ways to do it now. A simple test from your commandline to see if ssh is installed, type “ ssh“: On OSX and Ubuntu “ ssh” should be installed by default. Please comment if there are better ways or if something doesn’t work for you. So I cannot guarantee that the way how I’m doing it works for you, too. I read many blogs and documentation and it seems that there are many ways to have success with ssh where others fail. In part 6 from my blogseries I’ll describe some usual workflows while using a DVCS – and I’ll always try to find ways without the need switching to the commandline. You’ll have a better feeling what happens using EGit and HgEclipse and you’ll be very thankful to the developers of EGit and HgEclipse making your life easier. On the other side it’s always a good idea to know what happens behind the scenes, so I recommend (at least for one person of your development team) to go to the process and try making all from the commandline. If you’re using Mercurial under Windows or your workflows are missing some functions from EGit or HgEclips, then you need to work from commandline, too. Unfortunately at the moment only EGit uses Eclipse-SSH2 – would be great if HgEclipse could use it too – would greatly simplify work on Windows. if you’re working on windows and only using Git. If you skip the commandline – part and scroll down to the last part “ Eclipse Preferences SSH2” you’ll see that you can use ssh and also generate key-pairs from inside eclipse without the need of a commandline. Eclipse SSH2: the easy way to ssh and generating keys
SSH (Secure Shell) is a protocol for creating a secure connection between two computers. SSH provides authentication and encryption.
There are already step-by-step instrcutions to install Git and to install Mercury.Īccessing a remote Repository it’s a good practice to use ssh. Reverse this once you’re done troubleshooting, or when you see the Test Successful message in TeamCity.This is an add-on to part 4 of my DVCS – blogseries: – working with remote repositories of Git and Mercurial. This time, if there were any errors, you’ll be able to see them. When you’ve done that, the service will run as a console application, and you’ll be able to see the output. and check the Allow service to interact with desktop checkbox.
Part 2: Configutre TeamCity to use Mercurial Press Yes to save the key without a passphrase. You will be warned that your key is not passphrase protected.
Part 1: Installing TortoiseHg and generating a cryptographic key-pair for secure authentication Here are the steps required for configuring Mercurial with SSH in TeamCity: For this, I will use a repository hosted at RepositoryHosting. We use TeamCity as our continuous integration server, and it took some trickery to configure it to recognize the repository. Side note: Hg is a symbol for Mercury in the periodic table. At Typemock, we’re making the change of moving our source control from SVN to Mercurial (Hg).