Will FishEye+Crucible work with Gitolite managed Git repos?

[jmo]

We have Git access managed through Gitolite (so authorized users don't need an account on the system.) Will FeCru work installed on the same server (Lucid 10.04) as the Gitolite owned repos?

[David Yu · Accepted solution]

I use gitolite with FishEye, and it works fine. You simply create a service user, generate a private/public key.

When creating a new repository, you will specify the location as "git@gitserver:location/repo.git"

You can then upload that private key to FishEye during creation of this repo. One thing to watch out for is the first time FishEye accesses git, it'll need a manual acknowledgement that this is a known host. You can disable StrictHostKey checks to avoid this in your ssh_config file.

There are some gotchas to watchout for in FishEye + git that you can discover on your own in jira.atlassian.com. Rebases, submodules, and occasionaly indexing speed issues are issues that bother me the most--but it's still functional enough for us at this point.

[jmo]

Thanks for the info David, I already have a user on the system named 'jira' so hopefully I can just install FeCru under that account as well and generate the keypair on that acct?

Also do you create your repos with FishEye now instead of using gitolite-admin to create new repos? Seems like you would have to use gitolite still to create it or no developers would have access to it?

Edit: Looks like it might not work as the 'jira' user account which the JIRA installer created originally, looks like a pretty limited shell

[David Yu]

It actually doesn't matter which user you install FeCru with since you are given the opportunity to upload a private key file when you add your repository. So you can just generate a new ssh key-pair with ssh-keygen. Put the public one in gitolite, and use the private one for FishEye repos.

I create all my repositories in gitolite-admin first...I have not tested with FishEye creating the repositories.