Adding a tag to git is very resource intensive in fisheye

We've started using git / bamboo / git-flow (sort of) to start tagging our releases... Every new tag though creates massive resource consumption for the server runining Fisheye. (status in administration for the given repo Adding ta [tagname] ([commit hash])

Is there any way to avoid this? It's a fairly large project, but why would this have to take so long (as to a quick git command everywhere else?)

6 answers

1 accepted

This widget could not be displayed.

The KB article Git Repository Indexing is Too Slow when Creating a New Branch/Tag suggests and documents a --Xenable-git-content-hash-resolving-heuristic flag that may help in this case.

So, indexing of b/t creations can be slow for Subversion and can be slow for git... is there a supported SCM backend which is NOT resource-intensive for Fisheye?

I'll try the provided solution when i have the time... It seems weird though that a 'special' flag would be needed for something that other systems (bitbucket / github etc etc) don't seem to have a problem with?

Since we've moved away from FeCru as our main introspection tool of our repo and into Bitbucket / Github we just dont see the added value of FeCru over something as trivial as i.e. Bitbucket. It's just 'better' (imho)

This widget could not be displayed.

We're having the same problem. We have a very large git repo with a very large amount of history, and tags take greater than 12 hours to process in FishEye. I've gone though the FeCru performance best practices guide already; is this normal for FeCru?

This widget could not be displayed.

I'm not sure. It's a private fork of the Linux 2.6 kernel. So I don't know what Linus et al did in the early days before they switched to Git - did they migrate it from bitkeeper? Or start fresh? or?

This widget could not be displayed.

Was it converted from other SCM?

This widget could not be displayed.

I'm not sure. It's a private fork of the Linux 2.6 kernel. So I don't know what Linus et al did in the early days before they switched to Git - did they migrate it from bitkeeper? Or start fresh? or?

This widget could not be displayed.

It was converted from SVN to GIT with full history (>10K commits)

It still remains a mystery to me for now if that has anything to do with it though?

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Sep 17, 2018 in Teamwork

The tools we make for teams? We use them every day at Atlassian to get shit done (and it works).

I’m Jess, a Product Marketer for Jira Software Server and Data Center, and now a huge fan of our products. Read on for a 90 day, new-hire perspective on what it’s like to standardize on the Atlassian...

43 views 0 3
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you