How do I delete tags from Subversion without breaking FishEye?

A Subversion branch or tag is a copy of a particular repository path at a point in time. This is denoted as the addition of a particular path.

For example:

r1577 | dgr02 | 2016-06-01 14:13:18 +0100 (Wed, 01 Jun 2016) | 1 line
Changed paths:
   A /tags/SVN-HOOKS-1.1 (from /branches/svn-hooks-1.x:1576)
CBST-654 : Added issueType checking functionality.

The deletion of a branch or tag is the corresponding removal of that particular path:

r1586 | dgr02 | 2016-06-02 14:55:22 +0100 (Thu, 02 Jun 2016) | 1 line
Changed paths:
   D /branches/CBST-417
Branch clean-up

When users are looking to clean-up old tags they will often perform this in in en masse manner - for example (different repository):

r42953 | luw07 | 2016-06-02 13:15:31 +0100 (Thu, 02 Jun 2016) | 1 line
Changed paths:
   D /Database/DB_RDM/tags/snapshots/DB_RDM-106.0.19
   D /Database/DB_RDM/tags/snapshots/DB_RDM-106.0.21
   D /Database/DB_RDM/tags/snapshots/DB_RDM-106.0.22
   D /Database/DB_RDM/tags/snapshots/DB_RDM-106.0.23
   D /Database/DB_RDM/tags/snapshots/DB_RDM-106.0.31
   D /Database/DB_RDM/tags/snapshots/DB_RDM-106.0.32
... 480 additional deletions ...

This causes FishEye to get in a mess because it is unable to retrieve all of the changes associated with the revision in a suitable time. In the example above, each tag has 12,000+ paths so the whole changeset (according to FishEye) will amount to over 6,000,000 changes.

This, understandably, can cause FishEye to timeout its processing of the revision as it's SVN Operation Timeout is by default 1 hour.

For a changeset containing 1,000,000s of items it's unlikely to complete the transfer of all of this data within an hour for FishEye to then process; however whilst this would mean that the changelog would stay up to date it means that it would be continually re-attempting index the paths within this one revision.

My Question

Okay - so what I want to know is what are people's recommendations for actions which I can take which will help FishEye to cope with these kind of changesets?

Things I can come up with:

  1. Increase FishEye's SVN Operation Timeout parameter to a very high value (e.g. 2 weeks) so that it actually manages to retrieve all of the data – this can however have an impact on the heap requirements for FishEye as it then needs to be able to cope with a very large changeset.
  2. Put a hook on the repository which detects whether a changeset is impacting multiple tags and reject the commit. This however won't cope with if someone (in the example above) were to delete the directory containing the tags – that would appear in the commit log as a single item deletion.

What other suggestions might folks have for how I can protect my FishEye instance / help users to work in a more intelligent manner?

1 answer

Hi David,

I believe the best option would be to set an Exclude Path matching the path of the excluded tag when removing tags, then restarting (not re-indexing) the repository. To explain this a bit further, when adding an Exclude Path then just restarting the repository, FishEye will not try to index any further changes on that path - this way, you would maintain that tag indexed and showing up in your repository, but new changes, such as it deletion, wouldn't be indexed. I'm afraid it's not possible to set this programatically once you delete a tag, though, since FishEye's REST API doesn't offer an endpoint for setting exclude/include paths - for this, there's a feature request you can check at, but please notice Atlassian doesn't offer ETAs for the implementation of new features. Please feel free to vote and add any comments to it, as well as adding yourself as a watcher so you can track its progress directly. You may refer to Atlassian's policy for the implementation of new features.

Furthermore, if you don't wish the tag to display anymore in FishEye, you can set a Hidden Directory for it, which will just hide the given directory.

You can read further about Exclude Paths at and about Hidden Directories at



Suggest an answer

Log in or Join to answer
Community showcase
Alexey Matveev
Published Saturday in Jira

How to run Jira in a docker container

Everything below is tested on Ubuntu 17.10. I prefer to use Jira in a docker container because: 1. I can install Jira with a couple of commands. 2. I can start and stop Jira just by starting and s...

393 views 6 8
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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot