We are running Crucible 2.8.1 and have configured it with our Perforce 2010.1 server. In our Perforce repository, we have many dozens of active branches that contain changes that we'd like to be able to review with Crucible across different Crucible projects. I'm not sure from the documentation whether I should configure a single repository in Crucible that points to everything (//depot/...), or if I should make several smaller repositories (//depot/eng/iOS/feature/featureA, //depot/eng/Android/feature/featureB, etc).
Using smaller repositories is tedious, because someone has to come in and create a new repository each time we create a new source code branch in Perforce (//depot/eng/server/feature/featureA). With several dozen new projects, that becomes messy and high-maintenance.
Using a single large repository covers everything. But I wonder if this is frowned upon for efficiency? What is the recommendation here? We are not using Fisheye, so I presume it's using build-in 'light' Fisheye.
Thanks very much for your help!
In case if you haven't review the Exclude path feature in FishEye especially for large , you might to check this feature. Detail on performance tuning available at:
We recommend splitting large repositories into smaller logical components (i.e., by product or project):
The advantages of doing that, according to the link above, are:
There's no need to create a separate repository for each branch.
If this answer was helpful, please allow me to ask you to mark my answer as accepted in order to have it in the top of the thread, also helping other customers.
Thanks in advance!
Hello! My name is Mark Askew and I am a Premier Support Engineer for products Bitbucket Server/Data Center, Fisheye & Crucible. Today, I want to bring the discussion that Jennifer, Matt, and ...
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