Share your experience using Canonical Bazaar

My main use case for Bitbucket is to collaborate on code, manage versions, then automate the software development life cycle, and design for professional teams to manage all repositories as well as for code reviews. I use Bitbucket for code preparation as well as code review.

The best features Bitbucket offers include code review, robust pull requests where a team can review code and leave comments, easy features for merging code, and the latest AI-powered insights, which includes Atlassian Intelligence that helps suggest code changes wherever team members want to change and identifies issues in broken builds while recommending reviews.

I use Bitbucket for automated pull requests, so whenever I use AI agents, they can automatically analyze code changes and generate comprehensive PR descriptions. That saves time for developers and ensures consistency across teams. Bitbucket helps me write code through an AI editor that can help write, summarize, and transform comments on my code, adjusting the tone of my responses to ensure clear and professional communications. Also, automated workflows, which I call robo-dev, are dedicated AI agents that can take actions on my behalf, such as handling code planning, performing code generation, and automating repetitive tasks at scale. Moreover, Bitbucket AI tools can act as an expert twenty-four seven, automatically scanning proposed code changes, highlighting potential bugs, spotting anti-patterns, and suggesting improvements before a human reviewer steps in.

Bitbucket has positively impacted my organization by saving time, managing code at one point, and helping track tickets assigned to team members via Jira. Everything can be managed from one point, making it very useful from both the Scrum and developer perspectives.

Bitbucket needs improvement as it has very limited cloud hosting options. With Atlassian phasing out its self-hosted server version, organizations are forced to choose between Bitbucket Cloud, which may not meet strict local compliance requirements, or a highly expensive data option. Additionally, Bitbucket is not competitive on pricing for scaling teams, as the free tier is great for up to five team members, but the jump in price for growing teams beyond five users can become steep compared to other repositories. Some enterprise users report that Bitbucket's stability can affect its speed when handling very large repositories, and though it has good support, the technical support team should be more active, as I have not seen them as active compared to GitLab and GitHub.

The limited cloud hosting options and pricing for scaling teams are two important areas for improvement.

I have been using Bitbucket for three years.

Bitbucket is very stable. Bitbucket provides the largest number of repositories with larger code, and I have not faced any issues related to stability. It is very good.

Some enterprise users report that while Bitbucket's stability and speed can degrade, it handles very large repositories at a very scalable moment.

I can rate customer support a nine out of ten as they are mostly available and provide quick solutions.

I had used GitLab before Bitbucket.

I switched from GitLab to Bitbucket because it depends on what tool the organization prefers. As a developer, I need to use what the organization is offering. Personally, I think people should go with GitHub if they are a solo developer or student or want to host public projects where others can easily find and contribute. Bitbucket is preferable if the company already uses Jira or Confluence or needs a cost-effective way to manage private repositories for small teams.

I do not have any relevant metrics at this time, but I see it can be useful for up to five team members. If more are needed, the organization must purchase extra at an additional cost. However, the deep integration with Jira means the organization does not need to pay extra because they can easily integrate with Bitbucket if they already have Jira. I can say the return on investment is very good compared to GitLab, but not better than GitHub.

Before choosing Bitbucket, I evaluated other options, including GitHub.

Bitbucket is deployed in my organization based on the client's requirement, integrated both on-premise and on cloud. I use AWS as my cloud provider. I purchased Bitbucket through the AWS Marketplace. I would recommend Bitbucket only if clients are using Jira or Confluence, and if they need a cost-effective way to manage private repositories for small teams, as it is a better option compared to GitHub and GitLab. I would rate this solution a seven out of ten.

Hybrid Cloud

Amazon Web Services (AWS)

I have been using GitHub for the last three years in both my college and current company. I typically use GitHub for code development, pushing and uploading files to GitHub where it provides version control. I pull and push my code from Visual Studio Code to GitHub for storing database code and other files.

In my college, I work with three to four students on the same project using GitHub. We create one GitHub repo and push every project into that same repo so all of us can use it without needing to download it locally. When we push into GitHub, we can have eight to ten members or even more working easily. GitHub supports collaboration, whether in a small group or larger, making it easier to share code and organize everything in one place. All I need to do is push from my computer, and they just need to pull into theirs. Initially, I had difficulty understanding at the beginner level, but now I know how to commit, how to push, how to pull, how to sync, and the different functionalities available.

GitHub hasn't positively impacted my organization because we have many developers, and we cannot manually add and share all the code easily. We can take one repo into GitHub, then manage it easily and use pull and push effectively, allowing 15 to 20 developers to work on one project efficiently.

GitHub provides easy storage and management of code, tracking changes and version history, supports collaboration, and allows us to keep our profiles updated. GitHub profiles are useful for industry levels.

Tracking changes allows me to note when I perform specific changes. When we commit the code, we can add comments regarding the changes, such as what functionality we added or what bugs were solved. This feature helps us track the code at the end of the day, showing what we have accomplished and what still needs to be added, providing effective tracking of changes.

I do not see areas needing improvement.

I have been working in my current field for the last four to five months with the company, and as of my study, I have been working there for the last four years.

GitHub is 100% stable in my experience.

GitHub handles more users easily and can also manage large projects, so it is completely scalable.

I have never reached out for customer support.

I have never used any other solution before GitHub.

I do not have to deal with pricing because my IT department provides it, and as a student in college, I use the free version.

I did not evaluate other options before choosing GitHub.

Every person needs practice to use GitHub. Whenever someone uses it, it becomes easy to understand. Without using it, we cannot grasp it fully. Practical experience and theory are different.

GitHub has made collaboration easier for my team. I have not faced any challenges because we find it easy to use. I only need to handle the database side, so I only need to pull and push within the built-in repo on GitHub.

GitHub always saves time and saves me a lot of time and energy.

If you are a developer who wants to store your code and needs to manage versioning, you can use GitHub for daily ease and to simplify your workflow. I would rate my overall experience with GitHub an 8 out of 10.

On-premises

Other