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.

It's a source control system. We have lots of source code and we wanted to move to Git and there are a lot of different Git solutions out there, including free stuff. But we liked the features of Bitbucket, because it takes off some of the sharp edges, so to speak. It's a more professional version than the free open source Git that's widely available.

We have a couple of different tools that allow us to tie source code changes to report bugs. It's integrated with our bug tracking system and also integrated with our requirement tracking system. So we have better facilities. We could integrate these solutions using command line "hooks", but when we do it all manually, it's not likely to happen.

Even with the automation, we've had some situations where we've had mistakes. Developers have integrated code into the wrong place by mistake, so there's a fairly steep learning curve.

Being in the cloud and using large repositories can be slow. They should improve synchronizing very large repositories.

I have been using Bitbucket for six months. 

It's pretty stable. We just had one incident where one of our developers somehow got access to somebody else's code using his own credentials.  He logged in like he normally does but could not see our source code; all he could see was somebody else's source code instead. That's a security problem. They cleaned it up somehow and the next time he logged in, there was no issue.   

We don't have any issues with scalability. And no issues with availability today. It's on the cloud that you look for is, it's accessible worldwide, it's always working and you don't have to rely on your IT to keep it running.

There are around 100 users in our company. Their roles are Developers, DevOps, and QA.

We use several different source control systems and it's a big deal to change.  All the groups that were interested have now made the jump. 

I haven't contacted customer support. When we had the incident with the employee logging in with his credentials, we called support and told them this one guy had a problem. Other than that incident it's been stable and available. No real complaints.

The setup was kind of complex. We started out with some simple examples and that was easy enough. But then when we went to migrate real code repositories, we had to get into what they call large file storage, which was complex to set up.

The deployment took about a month with a small focus group and I would say it probably took two or three months to get everybody comfortable using it.

We use it on the cloud. It's the latest and greatest. You don't have to pay for maintenance and you get automatic updates and hardware and backups and all that nice stuff. I paid a little premium for it, but you get a lot of benefits.

Licensing is on a monthly basis, it's available on their website. They have a free version, a pro version and then they have an enterprise version.  The Pro version is kind of the middle of the road for about $7 per user per month.

I would advise getting some Git training.  Something like 85% of all developers use Git. So it's like the defacto standard for source control.  Bitbucket is a brand of Git that has some nice features on top of the core functionality.

The biggest lesson learned was, we should've done a little bit more training for the developers. It was very informal and should've probably been more formal, not necessarily sending everybody to university or a class, but a little more hand-holding.

I would rate it an eight out of ten. I give it this rating because there was the integration with the other tools.

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.

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 code management.

The product's most valuable feature is output backup.

There could be more AI features included in the product.

We have been using Bitbucket for two years.

I rate Bitbucket's stability a ten out of ten.

We have 100 Bitbucket users. It is a scalable platform.

The initial setup process is easy. It involves linking a desktop and deploying the code into Bitbucket. It takes a few minutes to complete.

We implemented the product with the help of our in-house team.

Bitbucket is an inexpensive product.

I rate Bitbucket a ten out of ten. I advise others to experiment with integrating the product with other vendors for deployment.

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.