Reviews (1-7 of 7)
Score 5 out of 10
Currently, Bitbucket Server (formerly Stash) is being used as the primary version control system in my organization. This means it is being used pretty standardly across both operations and development teams. This also means it is allowing multiple teams to collaborate on code as any version control system would within an organization.
- Bitbucket is, as far as things go, good at being a version control system. In look and feel, it's very much like GitHub with regard to structure and browsing code.
- Bitbucket Server has quite a few integrations out of the box that make it pretty quick and not very painful to integrate other systems (Jenkins for example).
- When restoring from backup, Bitbucket Server does not re-enable plugins that were once enabled. This means anytime you rebuild you are left to either go with enabling all of them or disabling all of them and waiting for other downstream systems to break.
- Permissions on repositories and projects are not very straight forward. From a user interface perspective, it's a little unclear the first time how to lock down things like pushing to master for some but not others, how to all others to merge pull requests (thus pushing to master) as long as it's not their own change, etc.
- Reliability is a real problem with Bitbucket Server. Sometimes, for no apparent reason, it will just decide to stop working and require a full restart of the application (which takes a fair bit of time). Being the primary version control system, this means there are quite a few people unable to complete their work while these issues are resolved.
Read this authenticated review
Bitbucket Server would be good to use if you are not extremely reliant on the availability of your code at any given moment. If you have other systems relying on the up status of Bitbucket Server that can cause problems if unable to reach it -- you might consider going with a different product.
February 04, 2019
Score 10 out of 10
We use stash to host our code repositories. We have many different repositories stored on their servers. We also use it to create and manage pull requests and browse individual files and commits to the code base.
- It picks up changes to your branches immediately.
- It's very easy to do a diff and compare your branch with another.
- Pull Requests are very easy to manage. You can set specific requirements so that a branch cannot be merged until a certain criterion is met.
- I love how easy it is to browse code in the entire repo.
- Maybe implement a slider on the top of the Pull Request where you could slide between commits to see what was changed (similar to Crucible).
Read Dane Allen's full review
It works great for our large company. We have many different repositories and it handles them all nicely. If you're just doing your own small little project, you'd be better off probably using something like GitHub.
March 21, 2017
Score 10 out of 10
Stash is being used to handle pull requests from JIRA issues into our development and production branches. Also, it is configured to run builds for java applications whenever a pull request is accepted into development branch. It has a nice and easy UI. Also used to create branches directly if not attached to a JIRA issue. Its integration with JIRA is the big plus of this product.
Read Alexandre Amantea's full review
Stash is well suited for integration with JIRA. Control code changes in small or large teams is made very easily with Stash. You can assign code reviewers that will be responsible for the code merge. Its integration with JIRA made things very easy and productive. Using JIRA and STASH you are just a few clicks from submitting your code.
November 11, 2016
Score 9 out of 10
Stash is used primarily for version control of different modules of codes within various teams at Fidelity Investments. Ours is a cross functional team geographically located in different time zones. The development team works on a piece on code, pushes the code onto the Stash server, which is then pulled by the testing team for review. Upon final approval, the release engineering team pulls the code from server and moves across various environments. Continuous availability of correct version of code is big business problem that gets solved because of the usage of Stash.
- Projects & Permissions - Stash keeps you and your developers productive by providing a way to structure your repositories and manage permissions via a simple, yet powerful user interface. Stash is very easy to use, manage & administer.
- Essentially Stash gives two versions of interfaces to work with.
- Stash Repository hosted on a server.
- Atlassian SourceTree.
- Atlassian Sourcetree is a tool to work with a code in stash. The two 'web' and 'desktop' versions make working with code user friendly, intuitive and comprehensive.
- Connectivity to JIRA - Stash keeps track of all issues associated with commits. Users can use Stash to quickly see all issues associated with a commit, or use the Source tab on JIRA issues for an aggregate view of all the code changes that are related to a specific JIRA issue. With this information available, your development team saves time when tracking particular bug fixes or improvements.
- I feel Stash should allow direct download of the entire folder containing various files of code. It is cumbersome to go inside a folder to download an sql file and then come back to the folder to download another.
- With respect to security password syncing between Stash & Sourcetree, there should be a mechanism of automatic syncing of passwords. In urgency if I need to download a piece of code and pull doesn't work simply because the authentication fails.
- Sometimes Stash gives problems while pulling files with long file names. I feel this can be addressed and there should not be any such restriction.
Read Advait Deshpande's full review
Version control is a must these days with the amount and complexity of code continuously increasing at workplace. A scenario where an approver has to approve a piece of code, an analyst needs to compare two different commits and an end user simply wants to download and replicate an entire repository of code, Stash is very useful for it's intuitive interfaces, clean description of error messages and segregation of staging and non staging areas for files. I don't see a scenario where you cant make use of Stash in a software team setup.
September 28, 2016
Score 8 out of 10
We use Stash locally for projects that we just don't want hosted elsewhere. It gives our clients peace of mind, as well as gives our developers the tools they need for developing. Stash is very similar to the hosted Bitbucket, and recently was pivoted to be more in line with that service, however it is extremely easy and straightforward for a small agile team to host Stash compared to other options.
- Version Control Environment.
- Easy set up and maintenance.
- It is really really reasonably priced!
- The features aren't in parity with Bitbucket, but are getting better.
- Upgrading to new versions of Stash.
- Solving technical issues that pop up from time to time can be confusing.
Read Darian Rawson's full review
Stash is well suited when you want to locally host repos and manage your team without having to manage everything from a terminal. It works well for small teams with big clients that don't want their code hosted off site. This can make auditing and other processes for contract negotiation doable for teams that can't host things outside of their development environment.
April 13, 2017
Score 9 out of 10
We switched to stash from TFS across whole organization due some limitations that we facing at TFS, especially on branching. On top of that, my company is using some of Atlassian's other products as well such as Bamboo, JIRA and Confluence, and we wanted to integrate the process of CD/CI seamlessly so Stash is an ideal choice.
Read this authenticated review
In my opinion, Stash is well suited for all software houses, however you need to plan ahead because if you don't understand how branching works, it will be a disaster when the source code grows bigger.
March 27, 2017
Score 6 out of 10
Our entire organization uses Stash for all code repositories. We store code in repositories specific to applications. Each department has control over a section of repositories. Some applications are spread across multiple repositories when they have deep collections of dependencies or scripts. We also use the pull requests system of stash for all code changes. Most if not all departments require two approvers for every pull request to be merged.
- Integrations with HipChat are solid, informative, and easy.
- Pull requests are easy to comment on, discuss, approve, deny, and merge. It has a very intuitive workflow.
- It's difficult to create flexible pull requests that might need to be approved by 4 people and others by only 1 person. All pull requests require the same number of approvers
- Maneuvering through the git-components of Stash to look at particular branches, diff branches, or view tags can be difficult, tedious, or impossible. Direct support for some more advanced git actions would be appreciated.
- There is no readme concept (like in GitHub) for a repository.
Read this authenticated review
Stash is good if you can incorporate it into other Atlassian products, and it is certainly acceptable for simple operations, but it is not as good as other products out there such as GitHub or Gitlab. Stash has nothing to truly separate itself from the crowd apart from its integrations with the rest of the suite of Atlassian products.
Bitbucket Server (formerly Stash) Scorecard Summary
About Bitbucket Server (formerly Stash)
Bitbucket Server (formerly Stash) from Atlassian offers a self-hosted source code management solution.
Categories: Version Control
Bitbucket Server (formerly Stash) Technical Details