nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Scaling Fisheye/Crucible for a larger environment

Russell H

We currently host multiple SCM instances on different networks and we are looking at moving all these into one big enterprise class SCM system. One of our problems is that the smaller SCM instances include Fisheye/Crucible.

We currently have performance issues sometimes on the smaller instances when people try and do large code reviews and it can adversely affect Jira which is linked. This could have severe consquences if the entire site was using one big system.

Is there any known way of load-balancing and mirroring Fisheye and Crucible?

The other question I have is, is there currently a known way of performing single project migrates from Fisheye/Crucible into another instance?

Thanks,

Russell

Accepted answers

Daniel R

Hello Russell,

We've made some recent improvements in the way FishEye/Crucible interacts with JIRA (FishEye/Crucible version 2.9 and the latest JIRA FishEye/Crucible plugin) so I'd like to know what versions of the products you are using in regard to your performance issues. Unfortunately, we don't currently have a method to load balance or mirror a FishEye/Crucible instance. Perhaps one of our experts can help in this area. Please open a support ticket in our private JIRA instance at support.atlassian.com if you'd like me to assist in finding you a partner. Lastly, you can move repositories from one instance to another but you can't yet move projects -- the feature request is here:

https://jira.atlassian.com/browse/CRUC-681

In order to move repositories, look for this heading "How to Re-Index a Single Repository on a Test Server" on this page.

Thank you,

Daniel

All comments

Daniel R

Hello Russell,

https://jira.atlassian.com/browse/CRUC-681

In order to move repositories, look for this heading "How to Re-Index a Single Repository on a Test Server" on this page.

Thank you,

Daniel

Russell H

Thanks Daniel,

I thought that was the case, I just wanted to check.

I'll raise a ticket with Atlassian Support to see if anyone can point me in the right direction.

I've voted for that feature request for single project migrate. In the meantime, I'll start writing a script to interact the APIs and see if it can be done...

Cheers,

Russell

Sergey Svishchev

Russell, please share your findings, if you don't mind.

If API way doesn't pan out, I'm thinking of doing it on lower level (altering the database itself).

Russell H

@s2s:

No worries, will report back any info I get back from Atlassian on my support ticket for this one.

The problem we have is that even if we manage to get a single project migration working by using scripted API calls then we have the problem that this probably wouldn't be supported by Atlassian if anything went wrong. We really need the functionality to be supported since we run an enterprise SCM system.

Anyway, we'll have a go at scripting a crucible project migrate with APIs in the meantime just to see if it can be done...!