Add existing git repository using local path

Is it possible to specify just path of the local repository like: "/home/git/repositoryName.git"

Since the main git repository and fisheye are running in the same server, it should be possible to do it without any authentication. Just system user fisheye must have permissions to access the git repository, right?

I've tried it several times, but with no luck so far.

Getting errors like:



Unable to clone remote repository: /path/to/existing/repository.git - [fatal: Could not switch to '/path/to/existing': Permission denied]

Error testing connection.
Error talking to repository:

fatal: '/path/to/existing/repository.git' does not appear to be a git repository
fatal: The remote end hung up unexpectedly

at com.atlassian.fisheye.git.GitScmConfig.testConnection(
at com.cenqua.fisheye.RepositoryConfig.testConnection(
at com.atlassian.fisheye.spi.admin.impl.DefaultRepositoryAdminService.testConnectionFor(
at sun.reflect.GeneratedMethodAccessor620.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(

Connection failed.


The permissions are correct. Can anyone please tell me, what's causing this issue? Why the local git repository cannot be easily mapped via path?

We have a lot of projects and even more git repositories... It would much more comfortable if we don't have to create an ssh certificate for each repository instance in fisheye.

1 answer

1 accepted

1 vote
Accepted answer
Lukasz Pater Atlassian Team Mar 20, 2013

Hi Jakub,

it definitely should be possible. What version of FishEye are you running? Make sure that the user the FishEye process is running as has the permissions to access the directory, that the git executable is set up, and runnable by the user. You could also try using a file:// url (file:///home/git/repo.git/). If that still fails please enable debug logging, try setting the repository again and request help at

For your setup you might also find the FishEye Directory Scanner ( plugin useful - it allows automatically scanning and setting up all repositories in the given directory.

Best regards,


Thanks for reply. After all the problem seems to be in permissions. FishEye requires read permissions for others on the target repository which is very inconvenient.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published yesterday in Feedback & Announcements

How do you analyze GC logs, thread dumps and head dumps?

Hi awesome community!  In this article, I would like to describe the one of the toolset (service) for the analyze some problems on different Java-based instances, of course, as Atlassian admini...

104 views 0 7
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you