Bitbucket Reviews

Bitbucket's most valuable feature is the web interface, which is useful compared to other tools, has a lot of features, and is intuitive. 

I've been using Bitbucket for two years.

Bitbucket is very stable.

Bitbucket's scalability is good for a single location.

We used an in-house team.

I understand Bitbucket's cost is on the higher side.

Before implementing Bitbucket, people should be clear on the tools they will have to adopt based on their needs. It goes well with other Atlassian solutions like Jira or Bamboo, but integration with other third-party solutions is more complex. I would give Bitbucket a rating of 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.

Bitbucket is our source code repository. We use it as our source code reaction control system and for pool requests and engineer builds. It is integrated with Bamboo, which uses a CI CD pipeline to release our code to different environments.

Bitbucket has improved our organization because it has simplified and streamlined our developer communication code and review process. It is also much more visual. 

We have also integrated it with Slack. Whenever we do a full request, we get information comments in a pool request through Slack on our team channels. It's much easier to go to Bamboo and see if this code was released. This is particularly important if the code troubleshoots production-related issues. 

Bitbucket's traceability is great. Being able to see pool requests is just a great thing for collaboration.

Sometimes we struggle with searching on repositories. It is a bit challenging sometimes to pinpoint the code or repositories when just filtering by repositories. That search capability could be improved to become more intuitive. It should allow for, for example, searching for specific source files or repositories or searching the code inside the source files. That kind of flexibility would be helpful.

Of course, making the tool free would be great as well. Its cost is probably why it is not used very much in smaller companies.

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

Bitbucket is great when it comes to stability. However, we do see some challenges with Bamboo on that front. Sometimes Bamboo agents get stuck and take longer to process and build requests and releases.

I haven't experienced any issues with scalability. For five to 10 applications, it works great.

In our organization, some 200 people are using this solution. Most of them are developers. The product is being extensively used in the organization at the moment.

I have not had any contact with Bitbucket's technical support.

We are using Bamboo and Bitbucket simultaneously right now. Before Bitbucket, we were using CVS.

We made the switch over to Bitbucket as part of a company-wide migration to the cloud. CVS can only be deployed on-premise while Bitbucket is on the cloud. Also, the code review process for request concepts and the team collaboration Bitbucket facilitates makes it much more friendly and modern.

I was not part of the initial implementation team. We have a DevOps team in our company, so they set it up and once it was ready, it was rolled out to the development teams with a ready-to-use config. What we did, as far as deployment goes, is move our code from a legacy version control system to a new version control system. That experience was straightforward for me as a developer.

The initial setup was relatively fast. It took us about three days to migrate a small-to-medium-sized application from the legacy version control system to Bitbucket, for example.

Unfortunately, I'm not privy to this information. 

Bitbucket is definitely a tool to consider if somebody is still on CVS. It is a great tool and well integrated with Bamboo. Both Bitbucket and Bamboo are made by the same company, and the latter is there to connect the dots between the code and releases in production.

Our primary use case of this solution is as source repository. We use it to store all the source codes. So we basically use it for easy management of access to the source repository and creating pull requests. It also helps us to manage and get an overview of the different branches we have. It integrates into JIRA seamlessly so you can see the task effects on a JIRA task and Git.

What I liked the most about this program is that it integrates seamlessly with JIRA, which really adds value to our organization. I also like it as a pull request feature, even though that feature can definitely be improved.

I think the developers are constantly working on improving the pull requests support. It already works quite well, but there are still some issues with the support of the workflow and how to actually measure the time you spend on using reviews for pull requests compared to the time you actually use for doing the task. I am not really sure how that should be handled. I don't have a good solution for it yet. 

I don't have any issues with the stability of Bitbucket. It just works as it should.

The only thing I've experienced with the scalability is that you have to buy additional licenses when you exceed 50 users. That's more related to the cost model. I don't think I've experienced any scalability issues with it so far, however. I didn't expect to either because it's primarily hooked up to Git, that's the source repository.

Only when we misuse Git, like when we add large binary files to a source repository, it doesn't go that well. That's because we don't use it like it was intended to be used. It has nothing to do with Bitbucket - it's more about Git.

I haven't used their technical support yet.

I don't know exactly what the program costs, but it depends on how many users you have. We recently upgraded from 50 to 100 users, and I think it's public on the website. I am not sure. 

My advice to others would be that, if they are looking for a stable on-premises solution, Bitbucket is the obvious choice. They can even use it if they are looking for a cloud solution, but we have a restriction that we have to run it on-premises. Therefore I think it's the smallest, best solution for us. 

I think it's worth paying for the extra features because otherwise you end up spending a lot of time configuring open source products. 

On a scale from one to 10, I rate Bitbucket a nine.

We develop our own applications and all of our source code activities are managed and tracked on Bitbucket.

Bitbucket is a standard git implementation with perfectly coordinated screens, it's secure, and we have had no problems with it.

We are satisfied with the user interface.

The installation of Bitbucket on our server was not as easy as other Atlassian products, so it is something that can be improved. The same is true for the upgrade process. I have upgraded it twice, and it is similar to the initial installation.

I have been using Bitbucket for two years.

We have had no problems and I'm satisfied with the stability. We use it quite heavily because all of our applications and updates are handled on different branches in Bitbucket.

I cannot say much with respect to scalability because we are a small company with a maximum of five people who are using the product.

In the two years that we have been using Bitbucket, we have not needed any support.

Prior to using Bitbucket, we were using the freeware version of SVN. We switched because Bitbucket has better features, especially for source code maintenance.

The initial setup was a little bit complex. It requires more intervention on the Linux console than the other Atlassian products. You need to adjust more files, for example.

It took us about a month to deploy and three people were involved in the process. Only one person is required for maintenance because it is generally maintained by Atlassian.

The deployment was done by our in-house team.

We have seen ROI but I cannot easily quantify it with numbers.

We are using the minimum package with ten users and we are happy with the price because we are a small company. With our small number of users, our licensing fees are approximately $10 USD per month. There are no fees in addition to this.

We evaluated GitHub but we require our own server for source code management.

This solution is good and it covers all our needs. Periodically, I receive announcements from Atlassian, mostly concerning the security features. They are fixing the newly discovered vulnerabilities and also, there are some other improvements in the features. Normally, I am not affected by the new features because we don't require them.

My advice is to start using this solution because it works very well and we are very satisfied with the functionality. If somebody knows how to configure git for libraries then they can implement Bitbucket as well.

I would rate this solution a ten out of ten.

We're using Bitbucket for version control and deployment.

What I like best about Bitbucket is that you can use it for deployment, primarily if your IP addresses do not work well with your deployment scripts. You can use the tool to whitelist IP addresses during deployment.

Currently, what's lacking in Bitbucket is the assignment feature or the feature of giving permissions to other users.

I've been working with Bitbucket since 2014.

The scalability of Bitbucket is ten out of ten. Bitbucket has documentation on how to scale, and you can also communicate with the Bitbucket team for any scalability-related questions.

I have yet to contact the technical support team for Bitbucket.

Currently, we are moving from Bitbucket to GitLab for convenience, but at the moment, we're still using both solutions.

Setting up Bitbucket is simple because you can log in with your email account.

My team uses scripts developed on Ruby to do Bitbucket deployments.

Bitbucket is a low-priced tool.

My company evaluated GitLab.

I'm working as a software engineer.

My company has four Bitbucket users.

My rating for Bitbucket is nine out of ten.

I recommend the tool to others. One company even consulted with me, and I told that company to focus on Bitbucket.

My company is a Bitbucket user. There's no partnership currently.

Our primary use case is for source coding and continuous integration.

Bitbucket has helped improve our organization by speeding up our production efficiency and product delivery processes.

Bitbucket is an integral part of our CI/CD project.

I would like to see the integration with some of the cloud service providers improved.

I have been using Bitbucket for the past year.

Bitbucket does not have a problem with stability.

The scalability of Bitbucket is reliable and we have over two thousand five hundred product items in place and the solution is operating as expected.

Technical support is good. We are facing accessibility maybe once a month. This is a small number in comparison with others in the field.

The initial setup of Bitbucket is not complex but you need to have a good working knowledge of the infrastructure.

The implementation can be done in-house and takes two to three hours.

When it comes to licensing we have the standard plan.

I can definitely recommend using Bitbucket and would rate them a nine out of ten.

Bitbucket has a global way of collecting data from air conditioners and real-time data collection for global customers.

We like that it can be integrated with Jira.

We should be able to choose the size of the RAM or container classification. We would like to see more infrastructure for the code. The scalability could be improved.

We have been using Bitbucket for nine months.

I rate the stability a five out of ten. In our organization, we have a lot of microservices, so our project wasn't that stable.

I rate the scalability a four out of ten, and it could be improved. We have about 20 users.

The setup was okay, and it was well-integrated. We are using a subscription cloud.

GitLab UI is better than Bitbucket. The UI in Bitbucket could be better. Jira is also not easy to understand.

I rate this solution a seven out of ten. We want people to use Jira for an integrated approach between Jira and all the products. Regarding advice, If you want an enterprise-class product, I first recommend Jira, and then I would recommend Bitbucket.