Share your experience using Canonical Bazaar

We are using products that are already established, as we are a consultant company that is working extensively on Microsoft technologies. For the queuing products, we are using Service Bus, Event Hub, and Event Grid, the tools in Azure.

At Advania Sweden where I work now, we are working only with Microsoft. In my previous employment at ITAB, we had some resources in Microsoft's Azure, but for the integration work, we were using MuleSoft. In that case, we had some queuing products used in AWS.

Currently, where I work right now, we are only working with Microsoft tools.

For the queuing parts in Azure, we are using GitHub and Service Bus.

We are using Service Bus.

The team is working with Service Bus and I am involved in it. Sometimes I look into the DLQ messages and see what goes wrong and explore how we can do it better.

I am not deeply involved in GitHub security alerts. I work more as a technical lead and solution architect, so the developers are more involved in the GitHub aspects than I am.

The same applies to Azure Service Bus.

I have not heard anything else negative, and they are satisfied with GitHub. GitHub's integrations with third-party applications are quite good for the needs that we have today. We have implemented some features here. When I am ready with some tasks as a developer and I do a pull request, we automatically send that to Slack, to a Slack channel so the other developers see that I am ready with a pull request and can review it.

We have been working on artificial intelligence improvements as well, and improvement of that, so the development and delivery to different kinds of environments will be faster. I think that a slight improvement in that case would be beneficial. I think it is quite good now, but a little bit of improvement would be even better.

I am talking about their artificial intelligence capabilities.

I am not thinking about some specific aspects right now. GitHub works for us.

For the queuing parts in Azure, we are using GitHub and Service Bus.

I rate GitHub as an eight out of ten.

GitHub's pricing is quite reasonable.

The use of GitHub's API for automating workflows is done through automation workflows.

I would rate this review as an eight.

My main use case for Bitbucket is for code management, code, and pipeline.

In my team, there are multiple people from different domains, and we are working in a distributed system on the same feature or product, so we do code on our local systems, but at the end, we need to merge our code. Bitbucket is the best place where we can push our code.

As we are managing our code into Bitbucket repo, which is a place where we store the code of a particular product, such as any QSR app, we have a repo and we push our code into that repo. Every individual pushes their code and we merge it with the help of the PR review process. For CI/CD, the CI/CD pipeline is a feature provided by Bitbucket to enhance productivity and security, allowing us to integrate a security pipeline like SonarQube, automate the process of build generation, and anything else.

In our workflow, multiple team members push their code into their branches on Bitbucket, which offers pull requests where each team member generates a PR request for review. If there is anything missing or if any inconsistency is found in the code, it can be highlighted with comments.

Additionally, Bitbucket offers automation features, allowing us to automate the PR review process, and it has adopted AI to further automate the complete review process. With CI/CD, we can also automate the process of pushing code using Git pre-hooks to validate everything before pushing. We check if our SonarQube pipeline works fine, and if anything goes wrong, we receive an email that our pipeline has failed. If it succeeds, we can generate the build, either AAB or APK, and even distribute our app on the Play Store.

The best features Bitbucket offers include a user-friendly interface for code management, which I find to be easier compared to other code management tools. Bitbucket has a very smooth UI/UX, making it easy to see my branches and repo, apply branch restrictions, add rules, and manage Bitbucket environment variables accessibly.

Regarding the environment variable management, we use secure API keys, such as Google Map keys, which are paid and very secure. Keeping them in the codebase would violate security policy, so we put our Google Map key into Bitbucket's environment variable and fetch it with CI/CD.

Bitbucket has a very great impact on my organization, as all code, whether from backend, frontend, or PWA, is now in Bitbucket, facilitating collaboration among our large team on the same codebase. Managing code becomes easy. Without Bitbucket, manual code merging would create problems we cannot imagine.

While other tools could help manage code, the UI/UX Bitbucket provides makes it easy to find branches, resolve conflicts, and add comments during the PR process. Maintaining code is crucial in the software industry, and the code is the key value, especially for our QSR-based product.

Bitbucket is quite good from what I have used. I am okay with the current state of Bitbucket, so no additional improvements are needed.

I have been using Bitbucket for around the last six years.

Bitbucket is stable.

Bitbucket's scalability is totally fine and stable.

I have not needed to reach out to Bitbucket's customer support team.

Neutral

I previously used a different solution before Bitbucket, specifically GitHub and GitLab, but I switched based on my organization's needs for Bitbucket licensing. After starting to use it, I loved it for the smoother experience.

I do not know which cloud provider is used. I received access from my IT support team, so I am unsure if they are hosted on their infrastructure or using something else.

I am not the correct person to answer questions about pricing, setup costs, and licensing for Bitbucket, as a dedicated team manages those decisions.

Using Bitbucket obviously saves time for my team. Especially during the AI era, Bitbucket has started adopting features that integrate with other apps, which greatly saves team time, and project management becomes much easier along with code management.

With Bitbucket, integrating SonarQube has helped us run the pipeline smoothly, allowing us to generate APK and AAB files that we previously did manually. The ease of managing code has saved everyone time from manual code merging.

I did not evaluate any other options before choosing Bitbucket.

I would say if you want a complete package for code management that includes automation of the code, PR review processes, code security, and integration with other applications, you should definitely choose Bitbucket. We are only customers of Bitbucket. I am okay with the current state of Bitbucket, so no additional improvements are needed. I rate Bitbucket ten out of ten because Bitbucket resolves my major problem of manual code merging through automation processes.

It offers multiple automations, and we can integrate Bitbucket with other apps, such as Jira, which allows branches to reflect the ticket name, making tracking easier.