As I mentioned earlier, we're transitioning from subversion to git, and one of the things we need to do is convert from many-projects-per-repository, which is what we had in subversion, to one-project-per-repository for git. This is partly to make things nicer, and partly because it will make Jenkins work better. So, thinking in subversion-terms, I thought I'd have to do it myself, and even tried by renaming all the files in one of the projects into the upper-level directory, removing all the other projects, committing locally, and then pushing to a new repo. Royal pain.

And then, I came across

Continue...

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...