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; } } }

Changing Fisheye repository from Github to Stash - how?

Glen Coates

We're trying to transition from Github to Stash at the moment, and of course one side-effect of this is that our Fisheye / Crucible instance that tracked all of our Github repos is now tracking the wrong code.

Given that our Github repo was mirrored to Stash as per the online docs, I would hope that there is a simple way to just re-point the repo in Fisheye and have everything just magically keep working. But alas, this is what happened when I tried to do that:

http://cl.ly/image/2f303p2O1S2C

Is there any way to achieve this transition without dropping the repo from Fisheye and adding a new one? I can only assume that dropping the repo will be extremely destructive to our existing (long) history of Crucible reviews that link to that code.

Accepted answers

Conor

Glen,

You should be able to update the repository location, then reclone and reindex which will recreate the FishEye index without disrupting the Crucible data.

First step would be to make a backup :-)

All comments

Felipe Kraemer

Hi Glenn,

There is currently no way to automatically import Stash repositories into FishEye. However, we have an open issue to address this which can be tracked, commented or voted on here: https://jira.atlassian.com/browse/STASH-2589

As suggested in the above link, if you're using FishEye 2.10.0 - 2.10.7 you can try to use this plugin:

https://marketplace.atlassian.com/plugins/com.atlassian.fecru.reposync.reposync

I hope this helps!

Glen Coates

Hi Felipe,

Thanks for the response, but that's not really what I'm after. The solutions you're talking about are for automatically adding Stash repos to Fisheye. We only have a handful of repos so I'm not concerned with the manual effort of adding Stash repos to Fisheye.

What I am concerned with is preserving the history of reviews that we have (that stretches back years) based on the commits in our Github repo on Fisheye. What I want to do is remove the Github repo from Fisheye and add the Stash repo to Fisheye, and have all the Crucible reviews that reference commits from the old Github Fisheye repo now point to the Stash Fisheye repo.

Put another way:

- If I delete the Github repo from Fisheye, then add the Stash repo, will Crucible be smart enough to link up all the commits for the old reviews with the new Stash-based repo?

Conor

Glen,

You should be able to update the repository location, then reclone and reindex which will recreate the FishEye index without disrupting the Crucible data.

First step would be to make a backup :-)

Glen Coates

Thanks Conor - that did the trick.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

bitbucket-server

fisheye-crucible

github

fisheye-crucible-administration