Share your experience using Canonical Bazaar

I use the solution for my company's customers, for whom I take care of the version controlling of source codes.

The tool offers a limited pipeline structure. In terms of improvements, the tool should provide more pipeline structures. On the security front, Bitbucket doesn't provide much, making it an area where improvements are required. With respect to code review, the tool needs to provide more options and provisions so that it is possible to link and perform code reviews without a lot of hesitations or shortfalls. The aforementioned area can be considered for improvement in Bitbucket.

I have experience with Bitbucket for six to seven years. I am a user of the tool. My company also has a partnership with Bitbucket.

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

Atlassian has an architecture that supports scalability features, especially when you deploy the product on an on-premises model since it can support multi-node functionality.

My company deals majorly with enterprise-sized customers who use the product.

I rate the technical support an eight out of ten.

Positive

The product's initial setup phase experience was good.

The implementation is pretty straightforward because there is not much you can do with the Bitbucket since it can be described as more of a repository-oriented tool.

The solution is deployed on the cloud.

The solution can be deployed in a week.

Bitbucket is available at a minimal price point. I rate the product price as two on a scale of one to ten, where ten means that it is a very expensive tool.

The product is predominantly used in the IT sector.

Bitbucket's collaboration is based on Git, so anyone can create codes with the same repositories. The collaboration process of Bitbucket is good, but there are a lot of limitations with respect to the functionalities, especially when we look at Bitbucket's competitors like GitHub or GitLab. Bitbucket is not at the level of GitHub or GitLab. Bitbucket is more for entry-level teams who don't want to get into security or the pipeline part of their product. For an entry-level team, Bitbucket is good.

In terms of the CI/CD pipeline, though Bitbucket has a pipeline, it is not so strong. The major advantage of Bitbucket is on the price front since its competitors offer tools at a very high cost. The products from competitors are offered at costs that are five times more than the price of Bitbucket. With Bitbucket, the pricing is minimal, and you get many functionalities.

Code review is not so solid in Bitbucket, so you can do only a limited set of activities inside Bitbucket. The pull requests part in the tool is actually good. I cannot see any standard features available in the tool, but it offers normal functionalities. Bitbucket has a lot of limitations in the reviewing part.

Bitbucket integration streamlines workflows since it has integrated with a lot of CIs. The tool also works with an open DevOps approach, though there are no ready-made or predefined plugins available, which allows you to just plug and integrate with the CI server. You can also go with webhooks or APIs as they give the diversity feature, allowing you to play with multiple products, after which you need not switch between products just for the sake of integrations.

Bitbucket handles large repositories or projects since it has Git LFS, so if we have a large file system, then it seamlessly integrates. The problem comes with the tool's memory-related capabilities since if you go with its premium plan, then it is good, but if not, then on a monthly basis, you need to renew your space, which can be a slight headache for a customer.

For an entry-level team in a company, Bitbucket is a good option. If there are people who want some advanced tool for version controlling of systems with CI/CD integrations, then they need to look at other options.

I rate the tool a seven to eight out of ten.

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

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.