We are indexing a large perforce depot and it looks like it will take a month or more just to complete the indexing. In the meantime we want to add another repository that points to the same perforce server but only 2 specific depot paths and start the changelist at one very recent so the teams can use Crucible for current checkins.
What will happen when the large repo indexing finally catches up and now for the 2 paths in the new repo, the same changelists are also being indexed in the large repo? Is this ok or will it run into trouble?
I guess this boils down to can we have more than one repository in FishEye pointing not only to the same perforce server but also the same depot paths on it?
Yes, that is a valid approach and FishEye will handle that fine.
Ensure that you have 'store review content' enabled on the project, so that when the larger repo does catch up, and you switch to that and disable the smaller repos, your review content will remain in tact.
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