What is the detailed difference between Fisheye (git) Repository Hosting and Stash?

[childnode]

Im confused.

Stash seems to be a answer to github:enterprise but Atlassian already hat a product for that: FISHEYE

• Since Fisheye 2.7 there is also git Repository Hosting available in Fisheye.
• Stash user license is more expensive than a fisheye license.

So why shall we buy and use stash?

What are the detailed differences?

Anyone who has a clue what' atlassian's "masterplan"? Will git repository hosting be removed in future FeCru version?

----

EDIT: more and more "featured" plugins are upcoming like https://marketplace.atlassian.com/plugins/com.stiltsoft.stash.graphs (yes, it's third party but you are teasering it) making stash the better fisheye?!
Next month, we'll see "Subversion support" for stash beeing "featured"?!

C'mon Atlassian! That's frivolous! Fisheye seems to be the first-born, but unwilled child ..
So I'm going to kickass fisheye AND stash ...

----

EDIT 2: It's getting weird. Fisheye Plugin for Jira now has support for Stash too.. Yeah, Atlassian you're just perfect in communicating "Stash will not superseed Fisheye" ... indeed, Stash supersed Fisheye (when using git, that's the fact! And the new "Light-weight Approval Process" is doing the same for Crucible!)

To summarise (from customer view):

Use FishEye if you want to: browse, search, visualise or connect source code hosted in Subversion, CVS or Perforce.

Use Stash for git

• if you don't need a full-text web search (what is ok in most cases as long fisheye was unusable here for a long time on big repositories so developers are used to search in IDE).
  also 3rd party come in here: e.g. Buccaneer
• visualization is available though 3rd party, e.g. Awsome Graphs
• connection to other systems is available too, see

Don't use Mercurial as long Atlassian doesn't support it neither in Stash nor Fisheye/Crucible is playing well with DVCS (This is the official cause, why Stash was implemented! see comments below)

Thanks for that kungfu kickass of product placement and marketing!!

[rverschoor · Accepted solution]

This is answered in the Stash FAQ:

Q: What about Git repository management in FishEye and Crucible?

A: The current Git repository management feature in FishEye will be deprecated in the near future. We encourage those interested in Git repository management to check out Stash. There is a promotional discount of 50% for active FishEye customers until June 30, 2012.

Q: Why did you create a new product for Git repository management? Couldn't you build this into FishEye?

A: We tried to build Git repository management into FishEye, and thought we could make it work. In FishEye 2.7 we added basic capabilities to host and manage Git repositories within FishEye. However, as we were planning future releases, we realized that the architecture of FishEye, built to index, browse and search across various SCMs, was not adequate for a DVCS repository management tool.

Therefore we have made the decision to build a new product, with a clear focus: hosting and managing Git repositories. Instead of a "Jack of all trades", we will have two products that are focused on 2 very different tasks:

1. Stash – Host, manage and collaborate on Git repositories
2. FishEye – Track, search and browse Subversion, Perforce, Git, Mercurial and CVS repositories in one place.

[childnode]

Thanks, just didn't clicked on the deep-depp FAQ link..sorry for that

What is unclear:

• What role will crucible get after deprecating this feature and forcing to move "forward" to stash. Do I have do include "stash" as an external application in Crucible? Currently I have to select the "Fisheye repo" which is assigned to a Crucible "project" to make Reviews work.
  As far as I can see (without testing and digging documentations) I have to index each git project twice. Once in Stash, once in fisheye for crucible ;( Doubled administration, doubled CPU time, …
• What features will be deprecated in fisheye and moved to Stash aside the hosting? I'm not willing to go to my boss again in 3 month telling him *oum* we must migrate another "feature" or "have to buy some new plugins to get back what was implemented in fisheye", …

Sorry to say that, but that's really boring! You guys are so "open minded" but so closed in communicating a "best practice to host a atlassian suite"

[jhinch (Atlassian)]

As a side note, to the comment above. Stash requires little to no indexing. The only piece of information indexed in Stash currently is the JIRA issue to commit relationship. This, even on large repositories, happens within seconds. All the precompution done in FishEye is not done in Stash

[Mark Douglas]

Thank you for your clear and helpful explanation

[Jens Schumacher [Atlassian]]

Do I have do include "stash" as an external application in Crucible? Currently I have to select the "Fisheye repo" which is assigned to a Crucible "project" to make Reviews work.

You have two options:

1. Use Crucible with FishEye – which allows you to review not only Git code, but any code across your organisation, whether it's hosted in Subversion, CVS, Perforce, Mercurial or Git. It also provides a nice integration with FishEye's interface for browsing and navigating source code.
2. Connect Crucible directly to Stash – in which case you would loose the click-through to specific revisions and other features that are provided by FishEye.

Regarding FishEye, we don't have any plans to deprecate other features. As was explained in the FAQ, we couldn't make repository management work for FishEye at the scale we need it to work and therefore decided it would be best to keep FishEye focused on code quality.

Generally, you can view FishEye and Crucible as code quality tools that help you search, browse, review and track changes to your codebase across a number of different version control systems.

Migrations from one VCS to another don't happen over night. At Atlassian, it took us more than a year to move over most of our projects, and we still have some code for older and not frequently updated libraries living in Subversion. FishEye and Crucible make sure that all that code is still accessible and reviewable when changes happen.

[Dan W.]

By Jens Schumacher [Atlassian] (505 karma) on May 16 at 4:24 a.m

2. Connect Crucible directly to Stash – in which case you would loose the click-through to specific revisions and other features that are provided by FishEye.

How can Crucible be directly connected to Stash? Found no way and no documentation about this topic. For me it looks like Crucible depends on FishEye and that's it with no way of integrating it into Stash.

Can you please comment the current status on Stash/Crucible integration?

[Jens Schumacher [Atlassian]]

http://blogs.atlassian.com/2012/07/linking-your-stash-git-repositories-to-crucible-for-code-reviews/

[childnode]

No need for it, Stash 1.3 has it's own "Crucible" called "Light-weight Approval Process" and "Code Review: Comment and Discuss"

see http://www.atlassian.com/en/software/stash/whats-new/stash-13

my opinion: just uninstall Crucible, save a lot of money, keep your users in ONE place/frontend
There is no (big) advantage when using crucible

[Mark Douglas]

Thank you for your clear and helpful explanation

[Jens Schumacher [Atlassian]]

EDIT: more and more "featured" plugins are upcoming likehttps://marketplace.atlassian.com/plugins/com.stiltsoft.stash.graphs (yes, it's third party but you are teasering it) making stash the better fisheye?!Next month, we'll see "Subversion support" for stash beeing "featured"?!

C'mon Atlassian! That's frivolous! Fisheye seems to be the first-born, but unwilled child ..So I'm going to kickass fisheye AND stash ...

FishEye has been build to allow users to browse, search and visualise source code for a number of different version control systems, and it is really good at that. It enables you to search the entire history of your source code and view reports that are otherwise hard to get. It also allows you to connect your source code to JIRA, so you know what changes are associated with a particular issue.

Do you need both, FishEye and Stash, when you only use Git? It depends on your requirements. Stash doesn't allow you to search for content across all repositories and does not have the level of reporting capabilities that FishEye has.

However, if you have source code in a number of different VCSs (eg. SVN and Git), FishEye allows you to keep track of all your code.

Will we release SVN support for Stash? No, SVN and other centralised version control systems are unable to support many of the features we have planned for Stash. That's one of the reasons why Stash was not build on top of FishEye.

To summarise:

Use FishEye if you want to: browse, search, visualise or connect source code hosted in Subversion, Git, Mercurial, CVS or Perforce.

Use Stash if you want to: host, manage and collaborate on Git repositories behind your firewall.