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.
Hello, Community! My name is Gosia and I'm a Product Manager on Jira Server and Data Center here at Atlassian. Since 2002 when we launched our public issue tracker, jira.atlass...
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