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

Continue...