Bitbucket Reviews

Bitbucket is supporting port management and when we're using Asana we can sync our old tickets with Bitbucket which has helped out our organization.

The most valuable feature of Bitbucket is its capabilities.

I have been using Bitbucket for five years.

Bitbucket is stable.

The stability of Bitbucket is good.

I plan to use the solution in the future.

I rate the support from Bitbucket a four out of five.

Positive

I have used GitHub and GitLab.

The initial setup of Bitbucket is quick.

I have seen a return on investment from using Bitbucket.

I rate the price from Bitbucket a four out of five.

Bitbucket is similar to GitHub and GitLab.

One person can maintain the solution.

This is a good solution that has many features.

I rate Bitbucket a nine out of ten.

My company uses Bitbucket for version control and codes that we use for transforming data.

I haven't gone deep into all of the features of Bitbucket. I use Bitbucket as a basic repository in my company, so I don't use it to deal with the CI/CD pipeline.

I haven't encountered any issues with the solution since I am familiar with the basic Git workflows. Most of my criticisms are directed towards Git and not Bitbucket specifically, so I can say that it can be a challenge to onboard new people who need to learn how to use the commit code in Bitbucket. In general, the aforementioned flaw is not a fault related to Bitbucket but more of a problem caused by Git and the knowledge gap that new users experience. Bitbucket can be made more user-friendly for new users.

Every solution nowadays makes use of AI to make their workflows easier for its users. Bitbucket doesn't currently offer AI functionalities. Though I am unsure how AI features can be incorporated into Bitbucket, I would like to see Bitbucket with AI functionalities.

I have been using Bitbucket for a year. My company is a customer of Bitbucket.

I have not faced any stability problems with the solution.

Scalability-wise, I rate the solution a ten out of ten.

There are around ten people in my company who use Bitbucket.

Apart from Bitbucket, I have experience with GitHub. GitHub and Bitbucket are almost the same. I don't have any preference between GitHub and Bitbucket since I don't use the tools to their fullest capabilities. I use the aforementioned tools as a basic repository in my company.

The initial setup of Bitbucket is simple.

The solution is deployed on the cloud. The development part of the solution is done on an on-premises model.

I recommend the solution to those who plan to use it.

I haven't explored the entire solution yet, so it would be best for me to rate the solution a ten out of ten after I do a deep dive into the product's capabilities. I rate the overall solution an eight to nine out of ten.

Our primary use case is for an ICM tool. Just source code. 

Bitbucket is significantly cheaper compared to GitHub and it provides on-premises hosting.

I would like to see the development operations side improved. The main challenge that we faced is implementing anything on the cloud. We need an improved automation feature for the cloud.

I have worked with Bitbucket now for four or five years.

The stability is very good. Even with the on-premises solution, we did not face any issues so far. I can only remember one or two times we may have had an issue.

Bitbucket is easy to scale and given that the cost, now I think even GitHub is charging based on the users for a team, but BitBucket is on-premises, and it has limitless scalability. We have six hundred users currently involved in working with coding.

I would rate Bitbucket a nine out of ten.

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.

We are using Bitbucket for the code checking and tracking of our project depositories which we have locally. This includes code changes in software development. 

Bitbucket has helped our company stay current with our updated code daily.

The solution is easy to use. If I need to check out my latest code or I need to send my local code to the depositories it is simple. Overall it is has been a good experience from my side using this solution.

One of the areas the solution could improve on is when there is a merging conflict it is quite confusing. When I am having a merging conflict I get stuck on the page, then I need to search how to handle the particular problem. For example, finding what the commands are which can be used. 

I might not have the proper knowledge of it. However, the merging processes can be difficult and could be made easier. Overall there should be better documentation available. When I first started out it would have been very helpful because I had to search to find out how to use the solution.

In an upcoming release, the solution could improve the collaboration. Additionally, there should be some startup tool or features for whenever we have local changes or updates it will prevent us from submitting any change unless they have been removed locally. For example, 
there should be some sort of command tool that can remove my local code first and then checking it by taking code from the latest one to resolve it.

I have been using Bitbucket within the last 12 months.

The stability of the solution is good. However, there have been times I had to close the program down and restart it.

The solution is scalable and it is not very difficult to do.

We have approximately 10 people using this solution in my organization which includes various teams, such as the automation department.

We use this solution every day and frequently, we plan to continue using it in the future.

I have used a previous version that was not user-friendly. Additionally, I have used GitHub.

We have one technician that does the maintenance of the solution.

I rate Bitbucket a seven out of ten.

We use Bitbucket in our company for source code management.

The most valuable feature of Bitbucket is its issue management.

Bitbucket should consider having a CI/CD if they don’t have it already. Bitbucket’s stability could be improved.

I have been using Bitbucket for ten years.

I rate Bitbucket a nine out of ten for stability.

Twelve developers are using Bitbucket in our organization.

Since it is on the cloud, Bitbucket’s initial setup is straightforward.

We have seen a return on investment with Bitbucket.

I use the latest version of Bitbucket. I would recommend users to use Bitbucket if they have the budget.

Overall, I rate Bitbucket a nine out of ten.

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.

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.