We are experiencing performance issues with our Fisheye instance and have started an exhaustive review of it's setup and hardware. One question we have is what exactly does the full scan interval control. Is there some best practice or recommendation for this default setting? Ours is currently set at 15min. If we understood better what exactly this does we might be better able to set it. We have an svn mirror setup on the fisheye server to reduce performance of networking to the primary svn server to capture each commit. What we have done is use a post commit hook to trigger an update to the mirror and then have our Fisheye repositories poll the svn mirror. Our current polling interval for our active repositories is set at 30s.
Full repository scan is an option for CVS repositories.
During an incremental scan FishEye checks the CVSROOT/history to determine what has changed in your repository. However, due to a fact that CVS may not be configured to create a history file, FishEye periodically runs a full repository scan to find new changes.
...word of mouth, so by 2016, we were working with several other entities on campus to implement Jira Service Desk . The Atlassian motto of “for every team” has really come true for us in this case. We...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot