While evaluating Crucible and FishEye we indexed a subset of our depot. Now we would like to expand it to include the entire depot. I was planning to change the depot path from //depot/something/something/ to //depot/
Just wondering if this will cause a complete re-index or will FishEye\Crucible only index the new data? It took around 2 weeks to index the subset so it would be nice to know what to expect.
Thanks in advance.
This action will require a complete re-index, because you'll be reconfiguring the repository location in order to include more folders and files.
In order to have a better idea of how long it would require to have that repository fully indexed again, a suggestion is to configure that repository in a test environment first.
We're concerned that it will take a month or more to index the data, which is not great. The indexer appeared to be single threaded (ie it only used a single core of the machine it was on), and was CPU bound. Is there any way to speed the process? Are there any plans to improve the performance?
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