In FishEye, we have a particularly large repository that we want to trim down a bit for performance reasons by using include paths (to only index trunk/ and branches/some-patterns-*).
It looks like FishEye wants to reindex the repository in order to put this into effect. Is there any way around a re-index? The repository is huge and usually takes around a week to reindex and I'd like to avoid the downtime if I can.
If I choose not to re-index, what will happen? Will it only skip non-matching paths for new updates? Will it restrospectively prune the existing index?
If you make changes to the Include and/or Exclude paths in the Allow screen, and Save them, you get a dialog:
A reindex required
A configuration change was made which requires a reindex of
[Ignore] [Perform now]
You can select Ignore, the repository won't be re-indexed then.
The changed Include/Exclude paths will then not be applied to the already indexed data.
You will have to restart the repository for the changes to be picked up (or restart the application).
If you already heard about Smart Commits in Bitbucket, know that you just stumbled upon something even better (and smarter!): Genius Commits by Better DevOps Automation for Jira Data Center (+ Server...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events