We have a rather large codebase in a svn repository, and one of our developers made the mistake of copying the entire repo into a branch (rather than just the trunk). He immediately deleted the branch, but this still means that Fisheye is trying to index the changeset. It's been > 24 hours and it's still working on the changeset. Is there anything I can do to tell fisheye to not bother with that?
I could add an Exclude Path, but wouldn't that force a full reindex of the repo?
You can tell Fisheye to start indexing from a particular revision but you can't tell it to skip a particular revision.
An Exclude Path is the least invasive way around this, I think. But yes, it will require a reindex.
Another way (just as time consuming because of the full index but fixes the problem for good) is to strip the revision history from your repo relating to the parts of this branch that were accidentally created. You would achieve this via svnadmin and svndumpfilter.
Sorry there aren't better options for you.
Here is a workaround for at least one case. If a perforce changelist is missing, you can decrease the block size to exactly 1. For some reason Fisheye can make it past the missing changelist number. Then once it makes it past the offending changelist you can increase the block size again back to it's normal value.
To reduce load on perforce and/or find which is the offending changelist, just cut the block size in half until you are down to about 10. At that point you can just run the "p4 describe -dn CHANGELIST" command on the remaining 10 changelists to figure out which one offends.
Hello! My name is Mark Askew and I am a Premier Support Engineer for products Bitbucket Server/Data Center, Fisheye & Crucible. Today, I want to bring the discussion that Jennifer, Matt, and ...
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!
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