Bitbucket Reviews

We use Bitbucket to store all of our code repositories. It has become the standardized tool for code management across all teams.

The platform integrates with other tools, such as Jenkins, enabling automated workflows for building, testing, and deploying code changes. It triggers the pipeline process, ensuring that builds are generated and deployments are managed efficiently.

The product could be less expensive for small companies.

We have been using Bitbucket for five years.

The product is stable. Being utilized by a multinational company like ours, stability is crucial, and it has consistently delivered on this front. Over the past five years of usage, we have encountered no significant defects or bugs.

We have around 1000 Bitbucket users in our company. On a wider scale, across India, where we have 22,000 employees, Bitbucket adoption is also significant.

The initial setup for Bitbucket was straightforward. The process was similar to deploying GitHub and GitLab, based on Git technology. We have various tools available, such as SourceTree or Visual Studio Code, which can seamlessly integrate with the product. I prefer using Git Bash for command-line operations. However, many others in our team utilize Visual Studio Code, which provides a user-friendly interface for running commands.

In a small-scale company where I previously worked, cost-saving measures led to a transition from GitLab's dedicated servers to GitHub's cloud-based solution. This switch resulted in significant cost savings and demonstrated the impact of cloud technology adoption on budget management. However, my current organization, a larger enterprise with a substantial budget, focuses on reliability and functionality rather than cost alone. Therefore, while Bitbucket may be perceived as costly for smaller companies, larger enterprises like mine prioritize tools like ServiceNow despite their expenses.

While alternatives like GitLab and GitHub were available, our organization remained steadfast in its preference for Bitbucket. Additionally, our team members, particularly those involved in DevOps, CI/CD, and system maintenance, were highly experienced with Bitbucket. Given the critical nature of our work in the banking and insurance sectors, where clients worldwide depend on our products, there was a reluctance to experiment with alternative solutions.

Learning to use Bitbucket, especially for beginners, is quite easy. In my experience spanning over twelve years in the field, most companies rely on Git for version control, and Bitbucket is just one of the platforms built on Git technology. The commands and client tools are the same: Bitbucket, GitHub, or GitLab. This uniformity makes it straightforward for beginners to adopt and use Bitbucket or any Git-based tool without facing significant challenges.

I recommend Bitbucket for version control features. It is a good tool suitable for long-term use. It's straightforward to adapt to, with user-friendly features and a convenient UI. 

I rate it an eight out of ten.

I use it to monitor developers' progress and occasionally check in on ongoing activities to stay informed about the project's status.

It is a highly beneficial platform for fostering collaboration among developers. Its key strength lies in securing and centralizing code repositories. Additionally, it excels in facilitating seamless integration and continuous deployment by offering essential capabilities for automating the deployment process and monitoring developers' progress and tasks.

It would be beneficial to have a straightforward mechanism for integrating the initial tasks defined in Bitbucket with Jira when the need arises.

I have been working with it for over ten years.

The stability of the system is excellent; we haven't encountered any issues.

I have been highly satisfied with scalability and I would rate it ten out of ten. Our project has seen growth from an initial team of around three to five developers to a maximum of eighteen, which includes additional roles such as the Project Lead overseeing the developers' progress. The team size typically starts small and gradually expands as the project evolves.

We didn't need to reach out to tech support. The majority of the issues we faced were successfully resolved through Bitbucket's online technical support and documentation. Our challenges primarily revolved around configuring and setting up pipelines.

When comparing Bitbucket and GitHub, we initially used on-premises GitHub, where we handled maintenance, including patching and updates. This became somewhat challenging and required more management efforts, prompting us to switch to Bitbucket.

The initial setup was straightforward.

The implementation is straightforward since the project involves a small team of around six developers who primarily focus on developing and enhancing the application. Currently, Bitbucket is not utilized for the QA or testing aspect, as testing procedures are manual, and automated testing has not yet been implemented.

We find that the pricing is very affordable.

Overall, I would rate it ten out of ten.

I'm mainly using Bitbucket as a code repository for storing the configurations and templates of my monitoring tools. We have them stored locally, and Bitbucket manages changes and builds, so we have a means of rolling back if there are any issues. 

There are about 10 to 15 users in the company at the moment. They want to expand usage, but there's still little uptake. It's an old-fashioned, traditional IT  place that they work in.

Bitbucket works fine for what I'm doing. It's slightly different from GitHub, but it's a good tool for storing code. 

Bitbucket's usability and integration with other tools could be improved somewhat. My other issue is that Bitbucket, GitHub, GitLab, and all the other ones use slightly different jargon for the same things. They should come up with a standard language for all these tools.

I have been using Bitbucket off and on for about five or six years.

BitBucket is stable. 

BitBucket seems scalable, but we haven't used it at scale, so I wouldn't know. 

Setting up BitBucket is fairly straightforward. It has its own APIs, and it's easy to access. Everything is in the cloud. 

I believe it's a monthly license subscription, but you get a discount for paying by the year, so I'd recommend that.

I rate BitBucket seven out of 10. If you're considering BitBucket, do your research and make sure it's the product for you. There are several options out there.

I use the solution mainly to control and share code within the team. I also use it to secure my parts and deploy my code. Overall, Bitbucket is for DevOps purposes.

We work on two or three different solutions, and we have some IoT devices that we collect some data from. That is a separate solution we use to identify customer flow and is on-premises. Though there is hardware for the basic part of the solution, we have cloud-based applications that collect data directly from that application.

Besides that, our primary ERP machine, an ERP server, dynamically provides financial operations. It contains everything about us and is cloud-based. Our third team is Power BI, and though it is cloud-based, the core is our data.

We collect data from all three sources for analysis and have a big setup for data computation, integration, and analysis. We use a database on-premises for that. We also use some Azure services, but not as much because we mainly use our database on-premises, and we integrate our cloud solutions directly with that. We have very high-speed Internet, so our customer and employee loyalty and mobile applications are different applications we use, all integrated with that specific database, and it is very smooth. Our primary applications are hosted on the cloud, and our analytical part is hosted on our private cloud.

Bitbucket is feasible and friendly compared to Visual Studio DevOps on the Microsoft platform. I have Visual Studio DevOps, Bitbucket, and Atlassian, and I found Bitbucket enabled more on a technical level because it grants access to those low-level things you can't access in Visual Studio DevOps, where you need to buy a specific part for that and integrate it with OneDrive first. With Bitbucket, you can easily integrate Visual Studio and use different tools. Also, when it comes to costs for the premium version, Bitbucket is lower than that part, and you still get the same level of access.

When users are given access for the first time, they should have some basic setups to help them specify their purposes. For example, when someone selects DevOps, they could get branches and trees created for dev, QN, and production deployment by default. Bitbucket could give access to the user from the front end to click and start working. The three setups mentioned would be very easy for organizations like Bitbucket to offer for free, for the user to create by default and just click and run.

Bitbucket must also incorporate the product with top-tier applications like Microsoft 365 and Microsoft Visual Studio. Other than Microsoft, Bitbucket could integrate with Oracle directly. Bitbucket could have these three foundation servers and Visual Studio at a very minimal cost, which would help businesses get some options. Bitbucket has to work in that market as well because this market has only one or two products already offered by top-tier companies.

I've worked with Bitbucket since 2017 or 2018.

I have not faced downtime because I don't know at what scale Bitbucket has been used. If I scale it to twice or thrice my site, I might face some problems.

When it comes to scalability, there's always a point for improvement, so I rate Bitbucket's scalability a seven out of ten. The solution is technically feasible, but when discussing scalable applications while targeting high-level customers, there is a problem with the customer interface. You don't always have a system admin with technical exposure when scaling up, so Bitbucket needs three setups. That way, when you scale up your customers, they can easily get the part.

We have a maximum of five people using Bitbucket at a time.

We contacted support recently because of some accrued repositories and received timely support.

The initial setup is not very complex on the technical side for us because developers, programmers, and operations people have a good idea of how to set up these things. You just need to know the audience using this type of application. Mainly, the audience would be system admins or developers who are technically enabled, so they don't face many hurdles or problems while working with the application.

I rate the pricing a seven out of ten because it is expensive. We pay about $500 or $600 a year for the Teams server.

I rate Bitbucket an eight out of ten.

We use the solution for source control.

The planning model is good, and so is the suite of applications around it. Bitbucket makes it easy to manage ops, integration, and unified login.

Bitbucket should come with code review pre-integrated, which would be better than integrating another tool into the solution.

The organization I'm working with has worked with the solution for about six months.

I rate Bitbucket's stability an eight out of ten for our use, keeping in mind we just use it for source control.

We have 20 users on Bitbucket. I have seen Bitbucket expand to hundreds of developers across multiple teams, and I didn't find any issues then.

My IT team has contacted customer support for Jira, probably to enable SS4. I didn't hear any complaints from the IT team that the resources were slow. They were able to resolve the issue pretty fast.

The initial setup is straightforward.

We managed the installation and configuration in-house.

I rate Bitbucket's pricing a five out of ten.

Comparing Bitbucket with GitLab, I would have chosen GitLab earlier because of its pricing model, though their new model has gotten a little expensive. Likewise, GitLab is better feature-wise.

If the organization has adopted Atlassian, I will choose BitBucket. Still, if somebody has chosen Visual Studio Online or Azure DevOps as their product management tool for their development activities, GitHub would be a better option.

Most providers provide scalable solutions, so that has not been something I've been concerned about. I'll know how to deal with it if I ever hit a hard limit. Likewise, hosting is not a big challenge. What concerns me is the service's features, whether it's BitBucket or GitHub. Similarly, I would be more concerned with creating the build pipeline, how well it's engineered, and supporting other platforms. For example, having the Mac OS or the iOS build tools available. A building environment is what I look for. And as long as the core repositories are working, scalability is my last concern.

When choosing a service, it's not just about the service alone but what the organization has adopted because that greatly determines what we choose. Otherwise, we would be competing with what the market provides in the future. 90% of future challenges would be because we poorly chose a tool.

I rate Bitbucket a six out of ten.

I use Bitbucket for plugins and Active Directory integration. It helps me onboard users for an automation suit. I also use it to check codes and generate reports on a daily basis. 

The tool's automation helped because we onboarded a lot of projects and teams into Bitbucket. The product's automation helped us complete activities in two days which previously used to take around two weeks to complete. We have completely automated processes that were earlier manual. It has good integration with Jira and Jenkins. 

Bitbucket should integrate a static code analyzer. 

I have been working with the product for two years. 

I would rate Bitbucket's stability an eight out of ten. 

My company has less than five users for the product. We use it daily. 

My interaction with the customer support team is good. 

Positive

I would rate Bitbucket's setup an eight out of ten since we had a lot of documentation available. We completed the tool's deployment over three to four months. We had a small team of two to four guys to help us with the deployment. One person is enough to handle the product's maintenance. 

We didn't rely on any third-party to complete the tool's deployment. 

Bitbucket is user-friendly and easy to configure. I would rate it a nine out of ten. 

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.

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.