Currently, FishEye scans 400 change sets at each time during re-indexing as below.
2012-04-09 00:12:56,541 INFO [InitialPinger1] fisheye.app SvnRepositoryScanner- slurpRevisionBlock - Slurping from 7526 to 7925
2012-04-10 09:33:46,134 INFO [InitialPinger1] fisheye.app SvnRepositoryScanner- slurpRevisionBlock - Slurping from 7926 to 8325
Is it possible to reduce the number to, say, 300 or 200?
The background of this question is when an error occurs during scanning, FishEye goes back to the initial change set of the block, therefore we would like to reduce the number of "lossed" change sets.
We appreciate your input.
This is controlled by the Block Size setting.
In the Repositories list, click on the SVN repo name, SCM Details, and you'll see the Block Size listed under SVN Options.
Don't forget to Save after you made a change.
When the field is empty it defaults to 400.
If you add a new repository you can set the Block Size straight away, it's shown when you click "Show advanced settings".
On October 20, 2021, Atlassian published a security advisory for Jira Service Management. The full advisory is available at this link. We've seen a number of questions already asking for...
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