Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,365,028
Community Members
 
Community Events
168
Community Groups

How to limit git history (shallow clone) in Crucible 4.5.0

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.

1 answer

1 accepted

0 votes
Answer accepted

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.

Best Regards,

Michael

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events