Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Fisheye: Is it a git repository or a viewer to a git repository

I want to double check that I understand Fisheye. Is it a web-based view to a git repository or is it a git repository as well? We currently have a git repository and have no need to migrate it, but we do have a need to view the contents of our repository in web based format. Is this ok?

1 answer

1 vote

FishEye is a revision-control browser and search engine not a repository by itself. You can use it to view the contents of your existing git repository.

If you want to browse your git repository but also manage it, you could try Stash, the new Atlassian product which focuses on Git.

Thanks Julien. I wasn't aware of another tool that was git-specific. Is Stash feature parity with Fisheye?

There is no full feature parity between Stash and Fisheye. For example, Fisheye is more integrated with Crucible (code review tool by Atlassian). In my opinion, Stash aims to be like Github Enterprise.

From Stash FAQ:

Q: Why did you create a new product for Git repository management? Couldn't you build this into FishEye?

A: We tried to build Git repository management into FishEye, and thought we could make it work. In FishEye 2.7 we added basic capabilities to host and manage Git repositories within FishEye. However, as we were planning future releases, we realized that the architecture of FishEye, built to index, browse and search across various SCMs, was not adequate for a DVCS repository management tool.

Therefore we have made the decision to build a new product, with a clear focus: hosting and managing Git repositories. Instead of a "Jack of all trades", we will have two products that are focused on 2 very different tasks:

  1. Stash – Host, manage and collaborate on Git repositories
  2. FishEye – Track, search and browse Subversion, Perforce, Git, Mercurial and CVS repositories in one place.

Thank you. Currently our evaluation of Fisheye is having problems connecting to our existing repositories that reside on another git server. Is this a limitation of Fisheye?

No, Fisheye is able to do that (cf. ). What's the error?


Unable to clone remote repository: git://HOST/ABSOLUTE/PATH/TO/REPRO - [HOST[0: XXX.XXX.XXX.XX]: errno=Connection refused, fatal: unable to connect a socket (Connection refused)] - Initialized empty Git repository in /usr/local/MACHINE/var/cache/REPRO_PROJECT/clone/

I am using No Authentication and the Authenitcation style since the Repro Location doesn't like the other styles. Any suggestions? Thanks!

I fixed the problems with our version of git on the server, but now seeing connection refused. We are using No authentication. Any suggestions?

Error testing connection.
Error talking to repository:

GIT_SERVER[0: IP_ADDRESS]: errno=Connection refused
fatal: unable to connect a socket (Connection refused)

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.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(

Connection failed.

I don't really know. If you try to clone your repository manually from the server where Fisheye is installed does it work?

I got it to work on Fisheye. The webserver needed to run as the person who has access to the git repository in order to gain access. However, I am having a problem speaking to the remote repository on Bamboo. Bamboo is running as a person as Fisheye, which is working, but this is the error I am receiving

Error encountered while triggering manual build: com.atlassian.bamboo.repository.RepositoryException: Failed to open transport for 'file:///SERVER/PATH/TO/REPO'.

Plan 'TEST' did not start

Can I get more information as to why this is failing? I am looking at the logs and I am not seeing why this is a problem.

Sorry, I don't know. I don't use Bamboo.

You should create a new question about this error, you'll have more chance of getting an answer.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events