Hi Rahul,
In brief, FishEye is a repository analysis tool that provides activity streams, dashboards, charting, advanced search capabilities, source browsing, notifications and other code-related features for a variety of SCMs, including Git, Mercurial, SVN, Perforce and CVS. It does not actually host your code, instead you point it at your repository and FishEye indexes it and provides deeper insight into your code base through its analysis features.
Bitbucket on the other hand is a SaaS service that actually hosts repositories for you. It supports just Git and Mercurial, and has a variety of repository management features, as well as some code browsing and review features (like Pull Requests).
The implementations of the two products have quite different philosophies as well, which drive the kinds of features that are implemented. FishEye has a heavyweight indexing process that generates all sorts of interesting statistics and search indices for your repository, which takes some time when a repository is first created, but allows for powerful charting and search functionality. Bitbucket on the other hand has a much lighter weight repository creation process (which means that repositories are accessible as soon as they're pushed) at the expense of some analysis features.
There is some overlap between the code browsing features of FishEye and Bitbucket, but they fundamentally serve different purposes (analysis vs. hosting) and can even be used in conjunction with each other. If you're hosting on Bitbucket but like the look of some of FishEye's features, you can add your Bitbucket repository to a FishEye instance and reap the benefits of both.
cheers,
Tim
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.