You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.
View groupJoin the community to find out what other Atlassian users are discussing, debating and creating.
Frequently, we copy our entire trunk as a branch. This is a lot of data, and takes Fisheye a long time to index this. While this is being indexed, other users are committing smaller changes that would not take Fisheye too long, but Fisheye is still stuck on the large branch creation. This causes a problem for us because we use Crucible to review, and Crucible cannot see those smaller changes because Fisheye is still indexing the large branch creation. Is there any way for those smaller changes to be seen and reviewed even if Fisheye is still working on the branch?
In general FishEye needs to scan the revisions in order they're created, so it needs to finish the branch creation before it gets to the newer commits.
If your reviews are mostly on trunk, you might consider creating a separate repository that just indexes trunk (or the relevant branches), and use that for reviews.
If you're experiencing excessively long indexing times on branch creation, try raising a support request on https://support.atlassian.com.
By default, FishEye uses one thread to process the incremental changes.
You can increase the number of Incremental Index Threads to 2.
One thread will then be busy processing the large commit, but it's no longer blocking, as the other thread will visit your other repositories to see if there are any commits in them.
See also https://confluence.atlassian.com/display/FISHEYE/Configuring+indexing .
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
3.0.0 increased the default numer of initial and indexing threads to 3 (FECRU-3329).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
FE3 speeds up svn indexing but it's still linear. But you should check if symbolic rules setup matches your actual repository layout.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That’s right! Grandma’s back at it again, and this time she’s brought all her friends. In honor of Team '21, this Bingo round is dedicated to all things team-related, and the prizes are no exception....
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.