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
4,254,242
Community Members
 
Community Events
164
Community Groups

Fisheye not indexing any Git remote branches

We've got a few Git repositories that we're indexing with Fisheye. We're trying to view the contents of certain remote branches, but it appears Fisheye is not indexing them (They're not listed in any branches drop-down, nor can I find them anywhere else)

The only thing being indexed is master

Is this expected behaviour?

4 answers

1 accepted

1 vote
Answer accepted

So the resolution to our issue was this:

Prior to using git, we used Subversion and had some extremely large repositories. For performance reasons, we mirrored our SVN repos to the Fisheye server so they could be accessed with the file:/// protocol. When we introduced Git repos, we assumed the same local performance benefits would apply. However, after cloning the repos to the Fisheye box, and having Fisheye index the local copy, the remote branches on the origin weren't visible.

To fix the issue, we told Fisheye to index directly from the master (over the wire) instead of indexing from the local clone. After doing this, Fisheye correctly displayed all of the remote branches

Hi David,

Currently I have 6 repositories on my Fisheye server.

I am facing same problem that you had mentioned initially.

The problem persist only for single repository while others are working absolutely fine.

I have tried re-clone and re-index on that repository but I don't understand by

"we told Fisheye to index directly from the master (over the wire) instead of indexing from the local clone"

How can I index master????

could you please explain this to me!!!!!

Thanks in advance.

 

0 votes
Nick Atlassian Team Aug 22, 2013

Thanks for the update, @David Corley.

Just an FYI - the way FishEye indexes both Git and Hg repositories is to first perform a bare clone of the repository to the local FishEye server. FishEye then processes the repository localy, via the file:/// protocol to keep things as performant as possible. Every POLL PERIOD, FishEye will first do a git fetch to retrieve an updates, before doing indexing those changes on the local clone.

Therefore, pointing FishEye to a remote repo should have no performance side effects for you.

Cheers,

Nick Pellow.

Hi David,

Could you please do these steps?

1. Go to FishEye Administration > Global Settings > Server > Debug Logging and click the Turn Debugging ON button.

2. Reproduce the problem.

3. Generate a Support Zip FishEye Administration >> Systems Settings >> Atlassian Support Tools >> Support Zip

4. Attach it to a support ticket to be investigated.

5. Go to ({{FishEye Administration > Global Settings > Server > Debug Logging}}) and click the {{Turn Debugging OFF}} button.

This way we can help you investigate why it's happening.

Regards.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira

#JiraHeroes May '22 Spotlight: Daniel Cave

At Atlassian, we take great pride in the software we ship, and even greater pride in the success our customers achieve when they use our products. #JiraHeroes is our new monthly spotlight series&nbsp...

471 views 0 6
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you