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?)
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)
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?
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...
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