Share your experience using Canonical Bazaar

Bitbucket serves the same purpose as GitHub, where version controlling, raising bugs, branches, and merging branches are involved. The same functionality is available, and we are using Bitbucket as per client requirements.

The integration with Jira is a feature I really appreciate in Bitbucket because it allows for easy task management integration, which is very beneficial. Bitbucket provides strong Jira integration, which is essential for our client who uses Jira for task management. This integration helps streamline processes and has built-in CI/CD pipelines, private repositories, and provides solid support for managing tasks effectively.

The CI/CD pipeline in Bitbucket streamlines our development process as we need built-in pipelines, which are available and easy to use. Bitbucket maintains code quality through branch permissions that alert you if you are pushing directly and there are branch protections or conflicts. It enforces naming conventions for branches, making it secure and easy to manage.

Security-wise, Bitbucket has good features such as private repositories, access controls, authentication requirements, and secure pull requests, ensuring safety at various levels. The initial setup for Bitbucket is easy as I log in with the company email to access a workspace. Creating repositories follows a straightforward process involving setting permissions and branch creation.

Bitbucket has less community support compared to GitHub, which has many users. However, if you are already using Jira, Bitbucket becomes a natural choice.

Bitbucket has limitations such as community support and built-in pipelines, while GitHub provides public access with many users and projects. Moreover, the UI/UX in Bitbucket is not as user-friendly compared to GitHub, where navigation can be confusing.

For scalability, I would rate it an eight. There are areas they need to improve on, including attracting more users and enhancing the CI/CD pipelines.

I am using Bitbucket for one of the projects from the past one year.

I would rate Bitbucket's stability at eight for its functionality.

I would rate scalability an eight. There are areas they need to improve on, including attracting more users and enhancing the CI/CD pipelines.

I have not directly taken technical support from Bitbucket as I deal with development, but based on the documentation and resources available, I would rate their technical support at seven.

Positive

The initial setup for Bitbucket is easy as I log in with the company email to access a workspace. Creating repositories follows a straightforward process involving setting permissions and branch creation.

Bitbucket has less community support compared to GitHub, which has many users. However, if you are already using Jira, Bitbucket becomes a natural choice.

The purchase plans for Bitbucket come from the client side, and they provide us access and details.

I can recommend Bitbucket to others, especially to those using Jira, as it makes task management much easier for them to understand and to raise pull requests or branches.

We will be using GitHub to store the version controlling, and we will be using it with some actions to merge the codes and raise the pull requests for one project, while for another project, we are using Bitbucket, which also has the same functionalities as GitHub.

The choice is related to project requirements, so according to client requirements, we will be using different platforms. For one project, we are using Bitbucket and for another project, we are using GitLab.

I would rate Bitbucket an overall eight out of ten.

When discussing my use case, I don't know which vendors we are working with in that area, as it's not my area of responsibility right now. About six months ago, I was promoted to Software Development Manager, and things could be different than they were before. I can give you another phone number at my company for the cybersecurity manager if needed.

I'm working with software development. We have a CI/CD process, and our repository is on GitHub with secure coding checks. We are using most of the DevOps processes in our company.

We can discuss GitHub further. I have been working with GitHub for about five years.

We are using GitHub because it is open-source software, which is the most valuable solution for us. The open source and community support are very good. We are always up-to-date with the community, and integration difficulty is very low. If you integrate any CI/CD solutions on GitHub, it's very easy.

We started using GitHub about three months ago with AI integration. For our deployments, some developers can be very shy about asking for descriptions on their commits. We are using AI support for comments and deployment management, which is beautiful.

We are not using the GitHub API for automating workflows in our projects.

I give GitHub a five-star rating for the review capabilities.

I also give GitHub five stars for integration with third-party applications. There is a lot of integration available on GitHub. If you want to integrate something, even if it could be integrated before GitHub, you can make your code and integrate your own in-house applications. It's a very easy and powerful aspect of GitHub.

Security could make GitHub better. OWASP Top Ten security advisors could be integrated on GitHub, and it could provide checks and advice. That would be much better. Additionally, LLM integration on GitHub could be a very impressive addition and is important.

We are using security alerts on the IDE. We are also a customer of JetBrains, and GitHub is good, but I think it needs a little development for the enterprise level.

I have been working with GitHub for about five years.

I give GitHub a four-star rating for stability because it's an open-source solution. There are some difficult aspects regarding deployment and high availability matters, but we can handle them.

I would rate the scalability of GitHub an eight.

GitHub's most competitive alternative is GitLab. I don't have any experience with other solutions, so I can't make strong statements about them.

The setup process for GitHub is very simple.

We are not using Citrix Endpoint Management. We have a different solution for endpoint management instead of Citrix.

We are not using Secure Private Access or the Citrix Cloud Platform.

GitHub Actions do not increase deployment time. It's actually a very powerful tool for deployments and was our first choice when deciding on GitHub. We have very easy deployments, and we have about two different development teams. Some of them are using Java, and some of them are using .NET. Both disciplines are very stable and have perfect deployment time on GitHub.

We are using forum support for GitHub, and we have a lot of friends on forums. Forums are very important to me. They were the first support on the internet, and I still love the forums.

I can recommend GitHub to other users. I give this review an overall rating of nine.