Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

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,460,441
Community Members
 
Community Events
176
Community Groups

Avoid full indexing after adding include path to large repository

Edited

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

 

 

1 answer

0 votes

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. 

Thanks for the clarification! 

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events