Avoid full indexing after adding include path to large repository Edited

[Ge Bai]

One of our Fisheye repository has been running index for two days becasue an include path was added.

The repository is fairly large, and we will be adding more include pathes in the fututre. Is it possible to only index the newly added path instead of indexing the entire repository?

We are using ''Atlassian FishEye Perforce analysis with Crucible code review. (Version:3.10.3 Build:20160112105703 2016-01-12)'

Thanks,

Ge

[Grzegorz Lewandowski]

Hey, it's not possible. Include/Exclude paths was designed in this way to include or hide certain paths from repository from user perspective.

In example, let's consider following changeset:

A directoryA/file1

M directoryB/file2

Let's say FishEye is configured in a way that include/exclude paths includes only directoryA  which determines shape of the changeset, file ancestry, diffs generation and basically every FishEye's feature. Once you change the rules to include both directories repository reindex is required to update the FishEye repository caches. 

*IF* you plan on adding additional include paths to a large repository what stops you from adding them as a separtate FishEye repository?

I'm assuming here they are independent since you don't need them all at once. 

[Ge Bai]

Thanks for the clarification!