I normally wouldn't be bugged by a scan that takes about 15 minutes but when you have developers that need to create reviews of code they pushed in, it's making the Crucible usage experience not that great.
What I'm seeing happen is when someone does a small commit/merge, FishEye does a git ls-tree that seems to recursively iterate each git object with this operation:
searching changeset ancestry of e0b9d469d62d02fe2933fd84d3b0385bc
I was somewhat prepared to expect a slow initial repo scan ( https://jira.atlassian.com/browse/FE-3461 ) but did not expect incremental polls to take this long as well.
Is there anything I can do to speed up the incremental scans? I've already tried adding EXCLUDE paths to directories where several thousand library files live but I'm still seeing the "search changeset ancestry" operation occur on these paths.
The repo has about 50 branches, and 7,000 files in master branch.
I am seeing the same issue on our largest git repository, but with delays of multiple hours. Fisheye appears to iterate through the entire repo each time the index needs to be updated, even when the intervening commits are very minor. Pursuing this issue with Atlassian support right now.
Hello folks, This is a series of articles where I explain GitHub Script with GitHub Actions and how you can automate publishing data on Atlassian & GitHub Platform based on the results of Workf...
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