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,363,404
Community Members
 
Community Events
168
Community Groups

Why is Fisheye indexing information before set revision that has been excluded?

We set up a Subversion repository in Fisheye and excluded a directory called "!deprecated". Then we set the initial import revision to be 12696. Many folders and files were copied into "!deprecated" in revisions BEFORE 12565, but on the initial import Fisheye wants to index all of these old files and folders in their former locations, even though they were moved before the set revision. Why? This is causing our index to take an unreasonable amount of time - now going on 5 days. It's reading that it's creating changest 12695, which I guess it has to do before it can start indexing at 12696, but why is it including folders and files that were moved into an excluded location before 12696? If it didn't do this, the index would've been done days ago.

2 answers

0 votes
Nick Atlassian Team Sep 18, 2013

In the Admin section, what "Initial Import" option have you got set?

Admin --> Repositories --> <repo> --> SCM Details --> Initial Import

Ensure that you have "Do not import" set.

I did have it set to "Do not import". That's one of the reasons it's concerning me.

I meant to say BEFORE 12696 - don't know why I said 12565.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events