Bitbucket Server (discontinued) Reviews and Ratings

Use Cases and Deployment Scope

Our organization uses BitBucket Server as our primary source control solution, across many different types of software - from front-end to back-end, or even to store configuration and documentation. It allows us to perform code reviews, link changes to Jira tickets, and facilitates enforcement of quality gates - all important in our increasingly remote workforce.

Likelihood to Recommend

BitBucket Server would work really well for small to medium sizes businesses who require a self-hosted code repository. It's less well suited for those who don't want to manage their own infrastructure, and would be better served by something like GitHub or BitBucket Cloud. Additionally we've ran into some small limitations as a large enterprise in regard to some configuration options, and it doesn't allow for zero downtime upgrades for major releases. Finally BitBucket's integration with Bamboo is great, but other automation tools might not integrate quite as tightly.

Use Cases and Deployment Scope

Bitbucket Server (formerly Stash) is used for some specific development units focused on software development for the business. Bitbucket Server (formerly Stash) has helped the development teams to overcome how they control the coding cycle in a collaborative environment with more than one group of developers working on the same project. Bitbucket Server (formerly Stash) allows the teams to handle the projects themselves and also to organize a portfolio of different products. Bitbucket Server (formerly Stash) is easy to deploy and manage using the internal or managed infrastructure on-premises or cloud servers.

Likelihood to Recommend

Bitbucket Server (formerly Stash) is suitable for departments or teams with the capacity to manage and support their own products and the availability to implement the tool on their own infrastructure. Bitbucket Server (formerly Stash) enables a good framework based on git to integrate the development cycle and to handle anything from a minor group of users and repositories to an extended usage with multiple users and roles collaborating in different projects.

Use Cases and Deployment Scope

Bitbucket is used mainly by the IT Application and Development team plus the IT Developer and Operations team. There are other departments using it, but with minimum interaction. It has helped a lot to produce better code, consistent deployments, testing and great collaboration with all the teams. Since we [started] using it, our internal clients' confidence in IT has improved.

Likelihood to Recommend

Bitbucket is well suited for private code repositories. There are tons of excellent integrations, including AWS, Microsoft Azure, Python, Visual Studio, Circle CI. and more. It is well-suited to support individual or team projects.

There are no scenarios where is less appropriate that I can think of, we use it in all our needs successfully.

Use Cases and Deployment Scope

Bitbucket Server is used as our main code repository for our development team. It is a distributed version control system so developers can still commit and track their changes even when they do not have an internet connection, and push the changes later when they are back online. Its pull request feature also lets developers to collaborate and review each other's work before changes are accepted.

Likelihood to Recommend

Bitbucket and GitHub are the two market leading products when it comes to distributed version control system, or using <b>Git</b> to be specific. You choice is going to come down to what <i>other systems and applications</i> you have in your organization. If you are using other Atlassian applications such as Jira and Bamboo, then Bitbucket would be a better choice due to its deep integrations with them out of the box, and you will get a 1 + 1 &gt; 2 experience.

Use Cases and Deployment Scope

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.

Likelihood to Recommend

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.

Use Cases and Deployment Scope

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.

Likelihood to Recommend

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.

Use Cases and Deployment Scope

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.

Likelihood to Recommend

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.

Use Cases and Deployment Scope

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.

Likelihood to Recommend

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.

Use Cases and Deployment Scope

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.

Likelihood to Recommend

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.

Use Cases and Deployment Scope

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.

Likelihood to Recommend

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.