Bitbucket Reviews

We use the solution for source control.

The planning model is good, and so is the suite of applications around it. Bitbucket makes it easy to manage ops, integration, and unified login.

Bitbucket should come with code review pre-integrated, which would be better than integrating another tool into the solution.

The organization I'm working with has worked with the solution for about six months.

I rate Bitbucket's stability an eight out of ten for our use, keeping in mind we just use it for source control.

We have 20 users on Bitbucket. I have seen Bitbucket expand to hundreds of developers across multiple teams, and I didn't find any issues then.

My IT team has contacted customer support for Jira, probably to enable SS4. I didn't hear any complaints from the IT team that the resources were slow. They were able to resolve the issue pretty fast.

The initial setup is straightforward.

We managed the installation and configuration in-house.

I rate Bitbucket's pricing a five out of ten.

Comparing Bitbucket with GitLab, I would have chosen GitLab earlier because of its pricing model, though their new model has gotten a little expensive. Likewise, GitLab is better feature-wise.

If the organization has adopted Atlassian, I will choose BitBucket. Still, if somebody has chosen Visual Studio Online or Azure DevOps as their product management tool for their development activities, GitHub would be a better option.

Most providers provide scalable solutions, so that has not been something I've been concerned about. I'll know how to deal with it if I ever hit a hard limit. Likewise, hosting is not a big challenge. What concerns me is the service's features, whether it's BitBucket or GitHub. Similarly, I would be more concerned with creating the build pipeline, how well it's engineered, and supporting other platforms. For example, having the Mac OS or the iOS build tools available. A building environment is what I look for. And as long as the core repositories are working, scalability is my last concern.

When choosing a service, it's not just about the service alone but what the organization has adopted because that greatly determines what we choose. Otherwise, we would be competing with what the market provides in the future. 90% of future challenges would be because we poorly chose a tool.

I rate Bitbucket a six out of ten.

I use Bitbucket for plugins and Active Directory integration. It helps me onboard users for an automation suit. I also use it to check codes and generate reports on a daily basis. 

The tool's automation helped because we onboarded a lot of projects and teams into Bitbucket. The product's automation helped us complete activities in two days which previously used to take around two weeks to complete. We have completely automated processes that were earlier manual. It has good integration with Jira and Jenkins. 

Bitbucket should integrate a static code analyzer. 

I have been working with the product for two years. 

I would rate Bitbucket's stability an eight out of ten. 

My company has less than five users for the product. We use it daily. 

My interaction with the customer support team is good. 

Positive

I would rate Bitbucket's setup an eight out of ten since we had a lot of documentation available. We completed the tool's deployment over three to four months. We had a small team of two to four guys to help us with the deployment. One person is enough to handle the product's maintenance. 

We didn't rely on any third-party to complete the tool's deployment. 

Bitbucket is user-friendly and easy to configure. I would rate it a nine out of ten. 

Bitbucket is the factor standard for development nowadays.

Git is Bitbucket's most valuable feature.

The module component needs improvement. 

I have been using Bitbucket for several years. 

Bitbucket is highly stable. I rate the stability a ten out of ten.

It is a scalable solution. We currently have 35 users. Bitbucket is extensively used.

I have previously used ClearCase and another server controller.

Bitbucket's initial setup is easy. 

A full licensing cost is paid for Bitbucket. 

I recommend Bitbucket to others. I rate the overall solution a nine out of ten. 

We use BitBucket as a repository for backing up our VS code. 

BitBucket is a reliable and user-friendly product. 

The UI could be a little better compared to competing solutions.  

I have used BitBucket for five months.

BitBucket is stable. We haven't had issues. 

I rate BitBucket eight out of 10 for scalability. 

I rate BitBucket support eight out of 10.

Positive

Deploying BitBucket is straightforward. 

I rate BitBucket eight out of 10. It's accessible to beginners. They can start by layering BitBucket and move on to other tools.

We use Bitbucket for managing and merging code versions, as well as for continuous integration when deploying code to different environments. It helps us to identify and resolve conflicts and to track the changes made to the code by different developers.

The most valuable feature of Bitbucket is you can see the differences between the fresh code and the old code before you merge. Additionally, the solution is easy to use and well-integrated.

Bitbucket can improve by integrating a tool to manage conflict code. This would save time.

I have been using Bitbucket for approximately five years.

The solution is stable. I did not find any bugs.

I rate the solution a ten out of ten.

The scalability of Bitbucket is not limited, but when there are many users it takes a bit of time. For example, every click that you do is slow sometimes. However, this issue might not have something to do with the number of users using it.

We have approximately 500 users using this solution in my company and it is used daily.

I rate the scalability of Bitbucket a nine out of ten.

I have not used the support.

This is a great tool that can help a lot to manage code between the environment, and merge codes and is highly stable.

I rate Bitbucket a nine out of ten.

Our primary use case is version control, integration with Jenkins for build management, and integration to Jira so that there is traceability to any issues from the build. We also work with code review and pull requests.

The most valuable feature is the bundle itself because we use them all. However, code reviews and the ability to support DevSecOps are very important.

The mandatory move to the cloud model is the biggest complaint. There are some minor things like customization, configuration, pricing, and limitations in general. I think the configuration can be improved because it is getting more complicated and not very well organized.

I have been working with Bitbucket ever since it was released ten years ago.

Bitbucket is definitely stable.

We were using GitHub before switching to Bitbucket. We do not trust corporations, because we do not want to make our private code available to these corporations. We do not want to just put it on a public site and therefore we switched to Bitbucket.

In the initial setup, you definitely need to be a developer or system administrator. I do not think it is for the faint of heart. You have to set up the reverse proxy and the DNS, so it is accessible from the outside world and make sure all the JVM settings are correct. 

We stay within the ten-user limit and it is affordable and we pay around one hundred dollars. However when you increase from ten people to anything higher the price increase to one thousand five hundred. That is unsatisfactory and they should have a gradual price slope.

I would rate Bitbucket a nine out of ten.

We use Bitbucket as a repository for our sensitive data, like source code and any other sensitive information that requires change and version tracking. We have eight to 10 users currently accessing Bitbucket.

Bitbucket is a standard source code repository with all the features you would expect. It supports Git and SVN. It's an extensive tool that provides us with merging, branching, and change management capabilities. You can compare the changes with the current and previous versions.

We have been using Bitbucket for four or five years.

Bitbucket is highly stable.

You can scale Bitbucket vertically or horizontally.

I rate Bitbucket support eight out of 10.

Positive

We used Team Foundation Server and Microsoft SourceSafe.

Bitbucket's Initial setup is a little complicated because you need to install  and configure the solution. It can take one or two days to deploy Bitbucket. If you have a high workload, you can deploy it on multiple server farms as needed.

The vendor is maintaining Bitbucket. We have one staff member responsible for the configuration, but we consult the vendor for patching and upgrades.

I rate BitBucket eight out of 10. Bitbucket is an excellent product. Atlassian will move to the cloud, so the on-prem version may be phased out. You have to be careful when choosing this product. There will be a cloud version available, so it's better if you go with the cloud version of Bitbucket.

We predominately use Bitbucket for continuous integration, as a repository for our code, and for various departments, such as analytics, web, and mobile.

Bitbucket could improve pipeline building and deployment. Our deployments are not using the Bitbucket. Deployments we are going through Azure DevOps, but the integration is happening in Bitbucket.

The repository and the access levels could improve.

I have used Bitbucket for approximately four years.

We have not had any issues with day-to-day usage of Bitbucket since we started using it.

We have not scaled Bitbucket that much to know the full range, but for what we use it for it has been good.

We have 10 to 20 users using this solution in our organization.

I have not needed to use the support team from Bitbucket.

The setup of Bitbucket is simple.

We have approximately 40 licenses for Bitbucket.

We did a benchmark before we chose our continuous integration environment. We found Bitbucket is the right tool for us at the start-up level. We conducted tests for Git, GitLab, and other solutions, but the decision we made was Bitbucket.

I rate Bitbucket an eight out of ten.