How do you synchronize an existing Fisheye/Crucible repository hosted on Bitbucket Server
Asked by Daniel Koverman:

My Fisheye/Crucible and Bitbucket Server instances already have an [application link](https://confluence.atlassian.com/fisheye/linking-to-another-application-385321667.html) set up. When repositories on the Bitbucket Server are added using the instructions for ["Add a Git repository that is hosted in Bitbucket Server"](https://confluence.atlassian.com/fisheye/adding-an-external-repository-298976885.html#Addinganexternalrepository-BitbucketServer), everything works great. Specifically, Fisheye/Crucible shows the Bitbucket repository as "Added" in the "Bitbucket Server repositories" tab and pushes to the repository [automatically trigger FishEye to run an incremental index](https://confluence.atlassian.com/fisheye/integrating-fisheye-with-bitbucket-server-587303683.html#IntegratingFishEyewithBitbucketServer-EasilykeepFishEyerepositoriessyncedwithBitbucketServer).

My problem arises for Fisheye/Crucible repositories which were created using the "[Add a repository](https://confluence.atlassian.com/fisheye/adding-an-external-repository-298976885.html#Addinganexternalrepository-Addarepository)" instrutions. As I would expect, it does not appear as "Added" in the "Bitbucket Server repositories" tab and does not get automatic incremental indexes. But it seems there is no way to correct this once the repository has been made.

**How do I configure a repository originally created in Fisheye/Crucible the "normal" way to get the benefits of Fisheye/Crucible + Bitbucket Server integration?** I was unable to find any configuration page on the front end of Fisheye/Crucible or Bitbucket Server which appear to be related to this functionality.

I'm aware of two workarounds:

* Create a hook on Bitbucket Server to notify Fisheye/Crucible to perform an incremental index. I do not like this approach because it requires re-inventing the wheel for something I should be able to get for free.
* Delete the repository on Fisheye/Crucible and re-create it using the instructions for a synchronized repository. I do not like this approach because it will lose all existing Crucible reviews. Some of these repositories have years of history.


Answers:
author: Piotr Swiecicki
body: Hi Daniel,

It doesn't matter if repository was added as a Bitbucket's git repository or with a standard "Add repository", as long as it's location URL matches the one Bitbucket Server is returning as clone URL. Ensure it is identical, paying attention to correct case of letters, spaces etc.

If you struggle, for your repository added via standard "Add repository" option, add it again as Bitbucket synchronised repository (the 2nd workaround you suggested), go to new repository admin in FishEye, go to "SCM Details" tab, "Git Connection Details" section, copy the "Repository Location" URL. Now you can remove the new repository created in FishEye, go to your original repository and past the copied clone location into same "Repository Location" field.

I just tested on my own, I can confirm I'm getting Bibtucket push notification pushed to FishEye even if repository is added manually.

Hope that helps,


Tags: application-link

bitbucket-server