End of Support Announcement for Internally Managed Repositories

On August 14th 2013, we are ending support for internally managed repositories. 

You can stay on older versions of FishEye to support your existing installations with Git repository management. However, Atlassian will remove all functionality related to repository management, from FishEye versions released after August 14th 2013. We are committed to helping our customers understand this decision and to assist you in migrating your repositories to one of the two other solutions offered by Atlassian if needed:

• Stash if you need to host your repositories behind your firewall
• Bitbucket if you prefer a SaaS hosting solution

Why is repository management being removed?

FishEye was built to enable browsing, searching and visualising source code in various Version Control Systems. With many customers requesting repository management, we have decided to provide a solution on top of FishEye. However, the part of FishEye's architecture that allows it to index different types of repositories and access your Subversion and Git repositories in one place, turned out to not be adequate for a repository management solution.

We have decided to focus on the core strengths of FishEye - browsing, searching and visualizing multiple source code management systems - and strengthen the product around these features. This also has enabled us to deliver a much more focused approach to Git repository management and offer a new solution – Atlassian Stash – which was build from the ground-up with repository management as a focus.

Going forward FishEye will continue to deliver new features and enhancements to help users browse, search and visualize across different Version Control Systems including Git, Subversion, Mercurial, Perforce and CVS.

My team manages Git repositories in FishEye, how do we migrate?

Here are suggestions to migrating your repositories to Stash or Bitbucket. The following steps will guide you through the commands that you need to run to migrate your FishEye hosted repositories to a different location.

We will assume that you already have a new repository ready to be used and that you have the latest local copy on your computer. In this case we will use a Stash example.

1. Create a new repository on the service you chose (Stash, BitBucket...)

This repository will be used as the new remote for your development.

2. Open your terminal and go to the local copy of the directory that you want to push.

cd /path/to/myrepo

3. Update the address of your remote origin to point it a the new repository.

git remote set-url origin ssh://git@stash.mycompany.com/MYPROJECT/myrepo.git

4. Push all the branches to the remote repository.

git push --all origin

5. Push all the tags to the remote repository.

git push --tags origin

At this stage all your local branches and tags should be present in your new repository and you can have the same development process as the one you had before.

7. Index your newly created repository with FishEye to be able to search, track and view report on your source.

Past this point the migration is complete – your repository should be hosted on a different service and indexed by FishEye as an external Git repository.

8. Delete your old managed repository

You will push and pull against your new service and FishEye will index the changes just like for any external repository.