Bitbucket Reviews

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.

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 to store the company's proprietary code and open-source projects and share them internally. 

Bitbucket works, and it's reliable 

I have used Bitbucket for five years.

I rate Bitbucket nine out of 10 for stability. We haven't had major issues.

I rate Bitbucket 10 out of 10 for scalability. 

I called Bitbucket support once with a question. I was pleased with their response. 

I use GitHub, which is also fine. We chose Bitbucket because it was a smooth transition from on-prem to cloud. We were already using the on-prem solution, so it was smooth and easy.

One of our guys deployed it, but I think it was pretty straightforward. 

I rate Bitbucket five out of 10 for affordability. It isn't cheap, but I think it's reasonable. The free tiers don't include everything I needed. I like to keep things simple. There shouldn't be all these features that you need to pay more to get. For example, some Atlassian tools have separate licenses, but others belong to a single Atlassian account. It's a little confusing. 

I rate Bitbucket eight out of 10. 

We have a Bitbucket server internally, that we manage with our own IT team. We use the solution as a software control repository.

Bitbucket could improve search and indexing capabilities. There is only basic searching available. There is only the ability to index the main branch but not the subbranches. The search capabilities are dodgy.

In a future release, the way they manage the permission of the records in the solution could be better. They fit well if you're only running one or two projects. If you have a lot of projects and records, the current permission model is not flexible. You have a challenge if you want to provide permissions across all the projects to be the same. Additionally, if you want to have specific permission there are limitations. There requires a lot of redundant work to accomplish what we want.

I have been using Bitbucket for approximately six years.

Bitbucket has some initial stability issues because of our large team using the solution. However, this was later resolved.

I rate the stability of Bitbucket an eight out of ten.

We have approximately 300 to 400 users using this solution. Our whole organization uses it.

I rate the scalability of Bitbucket an eight out of ten.

I have not used the support from Bitbucket. However, my team has used the support. The support has been fine, they have not had any downtime.

I have used GitHub and it has more features than Bitbucket. Additionally, I have used GitLab.

GitHub is a more mature solution compared to Bitbucket. The search capability has improved in GitHub since they are integrated with Opensoft. You can create your workflow and actions and it becomes easier to do things. GitHub can help a lot. The only season why our organization didn't adopt it is because of the high pricing.

The initial setup of Bitbucket is straightforward. 

The initial setup was in-house. However, it is possible they had some assistance.

Bitbucket is a cost-effective solution. It is the cheapest in the market. It is lower than GitLab and GitHub.

For general company usage, Bitbucket should fit the purpose. If you have a larger team you better look for other options. For a more complete solution for your CICD, I would recommend GitHub.

I rate Bitbucket a seven out of ten.

Our primary use case is for change management more specifically software development. 

The most valuable thing we have found is the workloads are good in Jira and we are able to control the access.

I would like to see the security logs option on the tool directly. The current way to work with security logs is through an email protocol.

I have been using Bitbucket for the past year and a half.

The stability is good and we have not had any issues.

Bitbucket is scalable and we have seventy-five to ninety users.

The technical support that we have received has been very good.

Positive

I have been working with Github and the organization decided to go with Bitbucket.

We used in-house support with Bitbucket.

GitLab was the other option and I have not worked with it. I do not have a personal preference between GitHub and Bitbucket.

I would rate Bitbucket a nine out of ten.