Bitbucket Server (discontinued) Reviews and Ratings

Rating: 4 out of 10

Score

4 out of 10

Community insights

TrustRadius Insights for Bitbucket Server (discontinued) are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.

Pros

Intuitive and User-Friendly Interface: Reviewers have consistently praised the product's intuitive and user-friendly interface, with many stating that it is easy to navigate and perform tasks quickly. This sentiment was shared by a majority of users. Easy Deployment and Platform Management: Users appreciated the product for its easy deployment process and efficient platform management capabilities. It provides a collaborative framework for the development cycle, which has been positively acknowledged by numerous reviewers. Seamless Integration with DevOps and ITSM Tools: The ability to integrate the product with different DevOps and ITSM tools has been highly valued by users. This feature allows for seamless workflow integration, as mentioned by several customers in their reviews.

Reviews

11 Reviews

One of the best, easy to use on-prem source control server software

Rating: 8 out of 10

Incentivized

October 21, 2021

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.

Pros

Pull requests / code reviews are simple but effective - it's easy to discuss the changes and enforce quality gates (through integration with Bamboo)
The access control model is fairly granular, with per-branch and per-action permission configuration options
There are various plugins available to extend functionality, such as SonarQube

Cons

You can't allow users to create new repositories without them being full admins of a whole project
There's not a way to limit who can merge a pull request (e.g. allow only the author to merge) outside of branch permissions
Some settings like default reviewers can't be easily copied to different repositories (without setting default reviewers at the project level, which we don't want to do because a single project has multiple team's code under it)

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.

Verified User

Engineer in Information Technology (10,001+ employees)

Vetted Review

3 years of experience

Bitbucket Server (formerly Stash) for code management and versioning

Rating: 9 out of 10

Incentivized

May 11, 2021

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.

Pros

Easy deployment and platform management
Provides a collaborative framework for development cycle
Allow integration with different DevOps and ITSM tools

Cons

Bitbucket Server (formerly Stash) should be evaluated for implementation based on the capacity of the environment ownership and support.
Insights and analytics reports are basic.
Bitbucket Server (formerly Stash) as part of Atlassian tools has some restrictions for centralized user management.

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.

Oscar Narváez Del Rio

Tools and Analytic Monitoring Leader in Information Technology at Entel (5001-10,000 employees)

Vetted Review

3 years of experience

View profile

Excellent Collaboration Solution for IT Teams

Rating: 10 out of 10

Incentivized

February 9, 2021

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.

Pros

Project management
Collaboration
Testing
Integration
Better deployments

Cons

Interface is not intuitive

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.

Verified User

Engineer in Information Technology (201-500 employees)

Vetted Review

4 years of experience

A bucket for your git code!

Rating: 10 out of 10

Incentivized

March 14, 2020

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.

Pros

Simple and intuitive UI.
Pull request for code review.
Good integration with other systems such as Jira for issue tracking.

Cons

Enforce rules on commit message format (although you can get this feature via 3rd party add-on), but this should be an out-of-the-box feature.
Lack of reporting and graph features.

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 > 2 experience.

Verified User

Employee in Information Technology (1-10 employees)

Vetted Review

5 years of experience

Living on the Edge - Using Bitbucket As Your Primary Version Control System

Rating: 5 out of 10

Incentivized

September 10, 2019

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.

Pros

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).

Cons

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.

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.

Verified User

Engineer in Engineering (501-1000 employees)

Vetted Review

3 years of experience

Stash: The best place to host your code

Rating: 10 out of 10

Incentivized

February 4, 2019

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.

Pros

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.

Cons

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).

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.

Dane Allen

Software Developer, Xactware Solutions, Inc. in Engineering at Verisk Insurance Solutions (1001-5000 employees)

Vetted Review

4 years of experience

View profile

Stash for GIT

Rating: 9 out of 10

Incentivized

April 13, 2017

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.

Pros

Auto merging is one of my favourite features.
Deep integration with bamboo.

Cons

Deep integration with bamboo for quality reporting which focus on commit (e.g. build failed)
Queryable engine reporting (like JIRA)
Guide template for branch strategy

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.

Verified User

Manager in Engineering (51-200 employees)

Vetted Review

3 years of experience

Functional but Free of Fun Extras

Rating: 6 out of 10

Incentivized

March 27, 2017

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.

Pros

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.

Cons

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.

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.

Verified User

Engineer in Engineering (10,001+ employees)

Vetted Review

1 year of experience

STASH and JIRA - Atlassian's must have

Rating: 10 out of 10

Incentivized

March 21, 2017

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.

Pros

Integration with JIRA
Easy to use
Review and accept code changes

Cons

More free plugins
Hooks examples
Better control of branches parents

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.

Alexandre Amantea

Senior Software Engineer (GIS) in Information Technology at Axxiom (201-500 employees)

Vetted Review

View profile

Atlassian Stash - Emergence of User Friendly Version Control

Rating: 9 out of 10

Incentivized

November 11, 2016

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.

Pros

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.

Cons

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.

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.

Advait Deshpande

Enterprise Analyst in Information Technology at Fidelity Investments (10,001+ employees)

Vetted Review

2 years of experience

View profile

Loading Reviews List....

Atlassian Stash - Emergence of User Friendly Version Control

Rating: 9 out of 10

Incentivized

November 11, 2016

Use Cases and Deployment Scope

Pros

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.

Cons

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.

Likelihood to Recommend

Advait Deshpande

Enterprise Analyst in Information Technology at Fidelity Investments (10,001+ employees)

Vetted Review

2 years of experience

View profile