We're transitioning, as a company, from Subversion to Git, which is a Good Thing, but has its complications. One of them was getting Jenkins, which we use for continuous integration, to work with our Git repositories.
I had started out by thinking that I would have to create a user in our repository provider (we're using BitBucket) which would have read permisisons to our repositories, a "jenkins" user. Turns out its not the case. All you need to do for read-only access is to generate SSH keys that you register with the repository, and which Jenkins uses to clone the repository.
On Linux, this would be trivial. On Windows, of course, very little is trivial.
So, following this guide(with some modifications) I managed it this way:
- Install Git
- Generate the new SSH keys on my local machine using
ssh-keygen. Make sure to specify a file other than the default (unless you like the idea of overwriting any existing keys you might have).
- Install the public key in the repository. In BitBucket, you do this under the account settings for the user or group who owns the repositories. Do it at the user/group level, not at the repository level (unless you want separate keys for each repository). Just cut and paste the contents of the public key to the web page, and click "Add"
- Install PsTools (Note: the link given in the guide mentioned above didn't work for me). Extract the zip file wherever you want (I put mine in the root dir)
- Run the following in a command shell running as administrator:
\PsTools\PsExec.exe -i -s cmd.exe(Note: the guide says use a normal shell, but that will fail the first time, because it tries to instal something that needs Admin privileges). To do this, find the command shell icon in the menu, right-click, and select Run as Administrator....
echo %USERPROFILE%in the shell to find out where the system user (and, hence, Jenkins) runs from as its home directory. Mine turned out to be
- Make a folder named
.sshin that home directory
- Copy the keys (private and public) to the Windows machine in the
"C:\Program Files(x86)\Git\bin\ssh.exe" -T email@example.com(Note: the location of git on your install may be different than mine). When you get the usual "unknown host" warning, type "yes" to get the server key in your known_hosts file
- Finally, test git by doing a
git ls-remote firstname.lastname@example.org:repo.git HEAD