Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements


  • Give kudos
  • My kudos


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How to best handle a changeset that causes indexing to hang?

As part of a cleanup task my team deleted a bunch of old tags and branches that were up to around 10 years old. (We were on CVS and migrated to SVN a few years back)

To do this, we deleted the tags/branches. We first deleted one that we did not care about - to test that we would in fact be able to restore it. It seems like this restore changeset is what is causing the indexing to hang up. The restore command we used is:

svn copy http://mkedevsvn99/svn/dnweb/tags/[tag-name]@15996 http://mkedevsvn99/svn/dnweb/tags/[tag-name] -m "Restoring branch."

To solve this problem we stopped indexing all tags by adding an exclusion (/tags/**/). First I tried to exclude just the one tag that was in that changeset, but it still got hung up on the changeset. Excluding all tags worked.

Unfortunately, we are now starting to regret that decision as it is hard to look in FishEye and see exactly what was committed before a tag was created. I read that it is not possible to just ignore one changeset - are there any other options here?

The only two I can think of:

1) Trying to exclude just the one tag again. I'm pretty sure I did it same as the exclusion now, except instead of the ** it was the tag's name. Re-indexing takes about a day so I would like to avoid kicking off a re-index that will not work.

2) Increase the timeout for indexing and just let it take as long as it needs to. This would take a long time each time we had to re-index.

I would appreciate any help/feedback.



1 answer

Hi Dan,

Excluding specific revisions is indeed not possible currently, but there is a feature request you can see at Please feel free in adding any comments to it as well as voting to create it's popularity and likelihood of being implemented in a future release.

For more information on how Atlassian implements new features and improvements please see the following document:

Increasing the timeout could be an option in case you are getting Timeout Exceptions. If you would like to try this, the following document will be helpful, as it contains the instructions on how to increase it:

I think another possible solution would be to set a Start Revision for this repository, which would be the revision number from which FishEye will start indexing the repository. For further information about SVN options, please take a look at

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Confluence Cloud

Share your Confluence Cloud experience for a chance to win $500!

Take our 5-minute survey to win a $500 Visa gift card! Are you currently using Confluence Cloud? We want to hear from you! Fill out this quick survey about your Confluence Cloud experience so we ...

153 views 1 8
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