Share your experience using Canonical Bazaar

I use GitHub for its repository, and I have also used it for GitHub CI/CD pipeline or GitHub Actions.

I have integrated GitHub with AWS Elastic Beanstalk service for code purposes and also in Azure App Service. After implementation, it is very easy to get code, and we do not need to use any cloud-related repository tools for code storage. So it is very easy.

I only used GitHub enterprise; otherwise, I mostly use the open-source version.

The best feature of GitHub is its branch techniques, and it is very useful for how the branches are managed. This is the best feature I prefer.

Applying GitHub Actions saves so much time for the team because it automates the developer's work to the server.

When working with the CI/CD pipeline and somebody is writing the workflow file, it would be best to include the AI feature so if they write incorrect code, it will notify me about it in the same dashboard, eliminating the need to use third-party tools to review the file.

I use GitHub as it is easy to get code, and we do not need any cloud-related repository tools for code storage.

When working with the CI/CD pipeline and somebody is writing the workflow file, it would be best to include the AI feature so if they write incorrect code, it will notify me about it in the same dashboard, eliminating the need to use third-party tools to review the file. I would like to implement the AI feature, especially in the workflow file.

I have extensively been working on GitHub for the past two years, and my total experience is about five years.

The initial setup of GitHub is very easy and not complicated at all. Especially when we apply it to the CI/CD pipeline as an open-source solution, it is very easy to implement.

GitHub is very stable for me with no performance issues.

GitHub is very scalable.

I have not used customer support for GitHub.

Positive

I was first introduced to GitHub, so I did not use any other solutions for coding purposes because GitHub was my first encounter.

The initial setup of GitHub is very easy and not complicated at all. Especially when we apply it to the CI/CD pipeline as an open-source solution, it is very easy to implement.

If you are new, especially for developers, it is very easy for the first implementation and pushing the code.

I would rate GitHub nine out of ten because if we have complex branch strategies, it becomes very complicated to manage all those branches.

GitHub is very stable for me with no performance issues.

I have not used customer support for GitHub.

I only use GitHub; I have not worked with any other version control systems or products of the same kind.

I have not used GitHub security alerts.

I also have not used GitHub API for automating workflows in my projects.

I am not utilizing code review capabilities in GitHub.

I rate GitHub 9 out of 10.

We mainly use Bitbucket for source code management, typically with all the dev repos and other third parties; the case resides in Bitbucket.

We have a number of dev projects residing in Bitbucket, and being a DevOps engineer, I mostly deal with this repo integration with the CI servers, Bitbucket, Bamboo, and Bitrise.

When a developer creates a pull request in Bitbucket, it automatically triggers a build in Bamboo, creating a build plan, and it starts building the dev changes and the new changes.

Bitbucket has a very clean UI, especially with the pull request dashboards where we can directly see the source and destination branches and the change, and the diff between the files in a single UI.

The security tools integration is very much easier, as for performing any SecOps activities, you can directly hook the Snyk or some other security tools with Bitbucket, and we have direct compatibility with various SAST tools.

Bitbucket doesn't provide any pipelines directly; we use Bamboo. We just hook the Bitbucket source code with a Bamboo pipeline as one of the jobs, one of the tasks in the pipeline activity.

We have a certain naming convention that we follow for the Bitbucket and Jira integration. If we have to create feature branches or any other branches with the name of a Jira ticket flag, adding the Jira ticket number in the commit message itself will directly sync with Jira, allowing a QA or developer to see the merges or commits from the Jira dashboard without opening the Bitbucket UI.

The branches in Bitbucket are purely a dev choice, and we follow a certain branching strategy including feature branch, bug fix, and other branches. For security's sake, if there is any hard-coded secret committed by the developers, we have the alerting mechanism, so we simply raise a notification and send it to the respective dev's mailbox.

These are most of the user-required features and functionalities available in Bitbucket, making it very user-friendly.

Sometimes the performance of Bitbucket is lagging; the UI loading part has some glitches at times, creating frustration for the developers.

Especially at the time of releases, when developers are actively committing, they want to access the tool more frequently, and at that time, developers experience some lagging and delay in the loading.

The only improvement needed is performance-wise, and if they can provide access to a dashboard where we can directly see the Sonar results and other third-party tools, it would be very time-saving for developers, QA, or the DevOps teams; as far as I know, that is not available as of now.

I have been working with Bitbucket for almost five years.

From a stability point of view for Bitbucket, I would rate it nine out of ten.

I would rate the scalability for Bitbucket nine as well.

I have had good experiences with the current agreements for Atlassian technical support, so I can say it's ten.

Positive

Setting up Bitbucket is very simple nowadays with the recent releases, mostly the cloud-based ones.

The in-house setup is very straightforward, and Bitbucket has provided their documentation; it's not a big deal to set it up—we can just spin it up in a day or two.

I would compare Bitbucket to GitHub as a main competitor in the market.

Comparatively, Bitbucket scores very well; in my opinion, Bitbucket is far better than GitHub.

I can say that Bitbucket is slightly expensive compared to other tools; I have already done that evaluation.

I purchased Bitbucket through the vendor only, and we have the Atlassian stack; we have taken the bundle license with other Atlassian tools as well, including Jira, Confluence, and Bamboo—not a single tool alone.

On a scale of one to ten, I rate Bitbucket a nine.