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.

Bitbucket's best feature is a Git client called SourceTree, which allows you to seamlessly integrate on-premise with on-cloud and mix and match repositories on your own server.

I've been using Bitbucket for four or five years.

Bitbucket's stability isn't flawless. It has crashed on me occasionally, but I haven't yet lost anything after a crash. I believe the client is written in C or C++ and should possibly be subject to a more rigorous testing procedure.

The initial setup is very simple - you use the web interface to create a repository, then receive a link and use it in your SourceTree client, and then you're connected. This is why I prefer Bitbucket to GitLab, because it's totally integrated and works with Jira, so everything is inside the same realm.

Bitbucket lets me create new projects in a few clicks and check out files in a seamless and integrated manner. It's also great for Linux users, including SourceTree running on Ubuntu, and for organizations that use Jira heavily. I would rate Bitbucket as eight 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 the solution in every project as a source control management software to control the versioning of the code.

The tool's UI is better. 

I would like to see the tool's desktop version. 

The solution is stable. 

I would rate the product's scalability a nine out of ten. 

I have used GitLab and GitHub before and I find the solution to be more user-friendly. 

The tool's deployment is simple and we use the cloud version. 

I would rate the solution a nine out of ten since its an awesome tool for source control and versioning. 

We use Bitbucket as our code repository and base it on our DevOps process.

This technology is quite common in our company. It is very important for our development process.

The version control feature for our code and the security aspect is valuable to us. It is also related to automation, DevOps, and our desktop environment.

There is room for improvement in the workflow. Other similar tools offer automation and more streamlined workflows, which Bitbucket currently lacks.

In additional features, I would like to see more low-code options for certain tasks. When we compare it to another solution like GitHub, in my opinion, Bitbucket could offer us more automation and actions in the future. This would be a valuable feature for improving our projects.

I have been using Bitbucket for around seven years. I use the latest version. 

It is a stable solution.

It is a scalable solution.

The customer service and support team is good. 

Bitbucket is worth the investment. Overall, I would rate the solution a nine out of ten. I recommend using the solution.

The solution is used for web-development

The solution is good for cloud collaborative work. During the time I was working as a release manager, I could manage the tool request and the technical problems that occurred on the site of the development.

We can watch the newly implemented code. So it's quite nice to organize the teams to see what part of the work is done and what part of the code is already old or new. It is very good for that kind of management.

The scalability for the cloud version can be improved.

I have been using the solution for nine months.

It is a stable solution.

It is a scalable solution. The cloud version is not scalable. But if you pay for the premium version it is very scalable. Five users are using the solution at a time.

I have only taken demos for products before and did not use anything. It was mainly the license solution. I was searching in several websites, and all of them were talking good things about the Atlassian solution. So I decided to give it a try.

The initial setup was easy and quick.

I deployed the solution myself.

I did not pay for the license as I was using a corporate license. But I think the pricing is fair.

It's very easy to use and a nice tool to manage. And I think the first implementation or the configuration is very important so that teams could work with that.

I rate it 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.