Crucible/Fisheye Re-Indexing Delima

Our situation:

We are currently having to re-index our entire perforce repository (81k changelists w/ over 5.3million files) -- Needless to say this is taking quite some time to perform.

Currently a lot of our product releases are held up because the newest of changelists can't be scanned due to the re-index processing other stages of it's operation. This is affecting many of our products.

Proposal:

Could I temporarily set up other repositories in FishEye to scan very specific directories so we can produce Crucible reviews then remove them after the main repository we have set up is caught up? By deleting the temporary repositories, would this affect any crucible reviews made off of them? Would this affect seeing the source code on the associated JIRA activities? Or would the fact that the main repository would then also hold that information and be caught up replace the identical changelists scanned?

I would like Atlassian's input on this one specifically, and definitely any user who has had experience with this in the past.

Alternative:

If this isn't a viable option... is there any way that I can get the newer changelists scanned while the re-indexing is processing?

2 answers

1 accepted

Accepted Answer
0 votes
Lukasz Pater Atlassian Team Feb 14, 2013

Hi Cameron,

The solution you proposed seems viable. You can either limit the new repo to a specific directory, or just set the Start Revision to a recent one - that should allow you to get it indexed quickly and start the reviews. (see https://confluence.atlassian.com/display/FISHEYE/Perforce for more details on this)

If the Crucible project the reviews are in has the 'Store the contents of files in reviews' option enabled (it's enabled by default) the source code in the reviews will be stored locally in Crucible as it is displayed for the first time from the repository, and you'll still be able to see it even after deleting/disabling the repository. (https://confluence.atlassian.com/display/CRUCIBLE/Setting+Crucible+to+Store+all+Revisions)

Once the temporary repository is finished indexing, you should see the changelists that are indexed there in the JIRA Source tab. After the main one finishes you might see them duplicated until you delete or disable the temporary one.

Though with the temporary repository I would have to link it up to the same projects in JIRA correct? Will that not cause an issue with 2 Fisheye repositories pointing to the same JIRA projects?

Any update on my last question?

Hi Cameron,

Yes, you can link multiple Fisheye repositories to the same JIRA project by adding entity links to map JIRA project to the required Fisheye repsoitories:

https://confluence.atlassian.com/display/APPLINKS/Adding+an+Entity+Link

Thanks,

Gurleen

You could also define a clone of this repository and index that clone, then replace the original index -- https://confluence.atlassian.com/pages/viewpage.action?pageId=298977103

Doing this automatically in background would be a very nice feature indeed.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published 13 hours ago in Jira Ops

Jira Ops Early Access Program Update #1: Announcing our next feature and a new integration

Thanks for signing up for Jira Ops! I’m Matt Ryall, leader for the Jira Ops product team at Atlassian. Since this is a brand new product, we’ll be delivering improvements quickly and sharing updates...

166 views 0 5
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you