We have a long history in git (~11 years), for our build machines we've been using a shallow clone. Reading https://www.atlassian.com/blog/git/handle-big-repositories-git suggests that's the appropriate thing to do with Crucible as well. How do you actually do it? I don't see any options in the configuration menu.
Michael Walker provided an answer, it seems despite this being the recommended action for supporting large repositories, Crucible does not support shallow clones:
While it is possible for Fisheye/Crucible to set include/exclude paths for your git repo, it is not currently possible to configure it to utilize a shallow clone. Having said that, there are several steps you can take to increase the performance of Fisheye to help speed things along. Additionally, you are welcome to have a look at our Best Practices guides and our Improve Fisheye scan performance.
Hopefully, this information is helpful, but if you have any specific questions that we can help with, please let us know.
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