I'm evaluating FishEye to be used in my company. Our only need is to index a very large Subversion repository with c# and c++ code to gain fast searching.
I have set up a single project (1 out of 100) and i takes ages to index the files (scanning 1.500 commits on that single project)
Can I set it up to only request and index the current version in SVN?
We don't need searching comments, diffs, JIRA integration or anything else, we just want to search the code as it is now in the trunk.
Thanks for clarifying this. Could you please check if setting a Start Revision as in https://confluence.atlassian.com/display/FISHEYE/Subversion helps? With this set you can have the indexing starting from a more recent revision.
If I understood correctly, your interest would be to index only the trunk (not indexing branches and tags). This could be done by setting the Path option as indicated in https://confluence.atlassian.com/display/FISHEYE/Subversion, so only the contents under it would be indexed. For instance if your repository root URL is http://localhost/svn/repo1 and under it you have directories named trunk, branches and tags, you would setup this repository as:
Please attend to apply any further configuration if necessary, e.g. if your repository structure doesn't follow the SVN convention as per in the Subversion Red Book please follow the instructions at https://confluence.atlassian.com/display/FISHEYE/SVN+tag+and+branch+structure.
Setting Include/Exclude Paths will take effect at the moment you restart your repository. You have the option to only restart the repository without re-indexing it, so files and directories which have been indexed prior to the update will remain visible in FishEye, and it will just not index further updates on these paths. By re-indexing the repository then everything defined as an "exclude" won't show up.
As per the file types, indeed you can't set them as an Include as includes do not accept antglobs or wildcards. I'd suggest you to add excludes for the file types you have in your repository that you do not with to be indexed.
For reference and further understanding on how to use Include/Exclude Paths, please take a look at https://confluence.atlassian.com/display/FISHEYE/Include+Exclude+paths.
Hi Stig, I understand you would like this as a feature. I research in our development issue tracker and found a request for this you can see at https://jira.atlassian.com/browse/FE-4212 I'm sorry to inform it is marked as Won't Fix. You can find further details explaining the reason in the comment contained in the URL above. Regards, Gustavo Refosco
Thanks for signing up for Jira Ops! I’m Matt Ryall, leader for the Jira Ops product team at Atlassian. Since this is a brand new product, we’ll be delivering improvements quickly and sharing updates...
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