Stash FAQ

Repositories

Q: I'm getting a "broken pipe" error when pushing my commits.

A: This error occurs when the amount of data you’re trying to push in one go exceeds Git’s http post buffer. Just run the following command to increase it to 500MB.

git config http.postBuffer 524288000

See Git push fails with 'fatal: The remote end hung up unexpectedly'.

Q: Does Stash support Mercurial (Hg)? What about other version control systems?

A: Currently Stash does not support Mercurial. We will be gauging demand for Mercurial support as we move forward -  STASH-2469 - Getting issue details... STATUS

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. 

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

A: 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.
   
   

Q: Does FishEye require Stash? Does Stash require FishEye? Can they be used together?

A: FishEye and Stash are two separate standalone products that do not require each other.

If you are using multiple source code management systems (SCM) at your organization it makes sense to use both Fisheye and Stash. While you are managing your Git repositories with Stash, you can use FishEye to browse, search and reference code from other SCMs including Subversion.

Also, if you are using Git, Stash will provide your Git repository management, and FishEye will be a central place to keep track of changes and search for code across your repositories.

Integration

Q: Does Stash work with JIRA? If so, what version of JIRA do I need to run Stash?

A: Stash works with JIRA 4.3+. However, you will require the latest version of the JIRA/FishEye plugin to view commits in JIRA.  See our documentation on JIRA integration.

Q: Will Stash integrate with any other Atlassian Tools? Crowd? Bitbucket? SourceTree?

A: Stash currently integrates with the JIRA issues tracker, SourceTree DVCS Mac client and Crowd user management solution. You can also connect to Stash via Bamboo to run your builds and deployments and we are planning even tighter integrations in the future.

Q: Will Stash be available for Atlassian OnDemand?

A: Atlassian Stash will not be available in OnDemand. If you are looking for a distributed version control solution to use with Atlassian OnDemand, we recommend using Bitbucket, our cloud based Git and Mercurial source code hosting solution. Bitbucket connects to Atlassian OnDemand via the JIRA DVCS connector.

Licensing

Q: Does my Stash license have to match the number of users in my external directory (LDAP, Active Directory, Crowd or JIRA)?

A:  No. You can control which users in your external directory have access to Stash, so that the license limit is not exceeded. A user is by definition any account that has permission to log into the Stash application. If you synchronise Stash with an external user directory, you can grant access to Stash to a subset of users, so as to stay below your license limit. The Global permissions page explains in detail how to manage login rights for users and groups in Stash.

Q: The number of users in my instance has exceeded my license count. Will Stash still work properly?

A:  As stated in the Global permissions document, any user assigned "Stash User" permission or higher, granted to the individual or via a group, will count towards the license limit. Stash will not allow you to grant the "Stash User" permission if this will exceed the license limit while manually adding users using Stash UI. However, if you happen to exceed the license limit by connecting your Stash instance to a User Directory that contains more users than you license allows you to have, Stash will display a banner with the content below:

To fix that bear in mind that users don't have to be removed from the database in order to reduce their license count. You merely have to make sure that they no longer have access to Stash via the "Stash User" permission through individual or group assignments.

Data recovery and backups

Q: Can I restore the .tar file created by the backup client into a database that is different from my original one (i.e. Oracle -> MySQL, etc.)?

A: Yes you can, as long as you specify all the jdbc parameters (jdbc.override, jdbc.driver, etc.) when running the restore. Please read Restoring Stash into a new DB for more details.

Q: I forgot the user/password for my old database schema. How will I perform the restore? How does it work?

A: As described in Restoring Stash into a new DB, the restore client will only restore into an empty home directory and an empty database. The new database should be configured following the instructions in Connecting Stash to an external database and its sub-page that corresponds to your database type. If you want to use a different type of database or a different user/password, you just need to specify all the jdbc parameters (jdbc.override, jdbc.driver, etc) when running the restore.

Q: What is the difference between the parameter pairs "stash.user & stash.password" and " jdbc.user & jdbc.password"?

A: stash.user and stash.password hold the credentials for a Stash sys admin user. They are only used during the backup procedure so that the backup client can lock Stash and instruct Stash to perform the database-agnostic backup.  The backup client does not need database credentials because the Stash system performs the database backup.

jdbc.user and jdbc.password are only used during the restore procedure when jdbc.override is set to true. They are used to connect to the newly-installed database.