I have used GitHub and GitLab before working on Bitbucket. There is no huge reason to choose Bitbucket over others. The only thing I like more about Bitbucket is security and user interface!
I have used GitLab and GitHub in the past. While GitLab is good if you are finding an open source solution for your code management and GitHub is good for the open source contribution, Bitbucket is an ideal choice to build an enterprise level product. The ecosystem that Jira …
When we make the choice of using BitBucket at that time we didn't have a choice. It was better than GitHub but nowadays GitHub is not just a source control tool it's a DevOps platform. If we talk about GitLab it is even better than GitHub. We're in the process to phase out …
Verified User
Employee
Chose Bitbucket
The main reason why we choose Bitbucket is because they provide a secure way to save the code using private repositories. The Access control is easy to setup too
Bitbucket is perfect for our business because it allows us to work on private projects and integrate seamlessly with our existing tools. They also provide a nice app called Sourcetree to help developers work on git environments without experience with git command-line …
When GitHub was acquired by Microsoft my previous organization had concerns about paywalls and additional restrictions that might be placed on the projects. We had made a move to Bitbucket as a result. The acquisition didn't seem to have any implications on the overall …
For the features we were looking at, Bitbucket, GitHub and GitLab were all at par and were in a similar price range. We found that GitHub was the most full featured should we need to scale very quickly. GitLab was at par with GitHub for our future needs, but GitHub was a more …
1. GitHub is open source and also many security vulnerabilities because it is open source. That's one of the main reasons we chose BitBucket. 2. BitBucket integrates natively with other Atlassian tools without any custom configurations.
Gitlab: Gitlab has a more robust code management and review system, but does not have any automated deployments so additional tools (such as Jenkins) would be required.
Visual Studio Team System (Azure Dev Ops) - VSTS is a better overall platform, since it provides a more robust …
I have used Tortoise SVN in the past with various teams. Tortoise SVN is open-source and has a lot of valuable functionality built in. That being said, Bitbucket is more user-friendly being that there is a decent user interface. The UI is not great, but it still makes working …
Bitbucket integrates with Confluence and Jira more easily than GitHub, which was a plus for us, given that we already used those tools extensively. Additionally, the pricing structure for Bitbucket makes it more affordable for our organization, which is especially important, …
Gitlab provides lesser features compared to GitHub. Gitlab/GitHub are both from a different company (Atlassian), which makes it tough to interrelate projects with other task management tools offered by Atlassian.
GitHub is a good repository to store and share code files. But GitHub is open to the community and public. But keeping the research codes private before publication is possible in Bitbucket.
Bitbucket is good for private repositories and reliable CI/CD integration but it's getting behind GitHub which every day has more and more integrations and which in my opinion has a larger customer group. Gitlab also offers some good support for private repositories but the …
We did select Bitbucket for a bit, but then we eventually moved away from using JIRA to different tools and as a result, it made more sense to move our source code to GitHub since it provides more features and is just much easier to use as everyone already knows how to use GitHu…
All 3 software works well for development and source code control, but for sure Bitbucket is the easiest to be set up and be deployed among the team. The integration with JIRA makes this a powerful tool against coding-only applications. However, for open source, it would be …
Of the three, we mostly use Gitlab the most. I don't know why as I was not part of the selection process. But if I'm to guess, this is an organization preference. Our company uses Bitbucket the most, while our partners either use Gitlab the most and sometimes ButBucket. But if …
At the time of making the selection, Bitbucket offered free private repositories when no one else did. This was the primary motivator. With GitHub, you can now have free private repositories on personal accounts, but organizations must still pay for private accounts. Overall Git…
Bitbucket was my repo host of choice when it came to private repos, but now that GitHub offers free private repos I’ll probably just use them. If you want to manage branch protection though you’ll need a Pro membership for GitHub whereas it was free with Bitbucket.
I think Gitlab and Bitbucket are very similar. I am very familiar with git commands so its easy for me to use both. But I would still prefer Gitlab since it has few additional features like send merge request, approvers etc.
From a cost standpoint, Bitbucket is the winner if you fall outside of the ability to use the GitHub and Gitlab free tiers. Both of those solutions have their own merits, but from a cost saving perspective Bitbucket is more than likely going to be the most effective option.
Bitbucket uses Git as a client which is more advanced with lots of features for source code management tool. It is very easy to scale horizontally as per our needs, and recent new features like adding multiple file systems keep Bitbucket more useful. Due to multiple file …
As a team we need to push code into the repo on daily basis, Bitbucket has proven that is a reliable and secure server to save and get the code available in no time. The administration part is really easy and there's an extra tool for every developer profile either if you want to use the console or a GUI like Sourcetree.
Very easy to integrate with other DevOps tools like Jenkins and with project/workflow management tools like JIRA.
Very efficient in managing security and compliance standards for code, especially during pull requests, merge requests, branching, etc.
Very robust in performance, especially the cloud and datacenter versions hardly hit any performance issues and supports more than 2000+ developers in my company.
All products have room for improvement. The system improves over time with better and better integrations and I look forward to even more features without paying extra! The system has increased transparency across my organization and with this transparency comes increased throughput on projects. I don't think I can go back to any other system and we are definitely married to this product.
The architecture of Bitbucket makes it more easily scalable than other source code management repositories. Also, administration and maintaining the instance is very easy. It integrates with JIRA and other CI/CD applications which makes it more useful to reduce the efforts. It supports multiple plugins and those bring a lot of extra functionality. It increases the overall efficiency and usefulness of Bitbucket.
The customer support provided by Atlassian (Bitbucket's parent company that also makes Jira, Confluence, etc.) is very helpful. They seem to be very concerned about any issues reported with their products and even just questions about functionality. They are constantly improving the products with new features in nearly every release. Plus they have a plethora of online documentation to reference.
For the features we were looking at, Bitbucket, GitHub and GitLab were all at par and were in a similar price range. We found that GitHub was the most full featured should we need to scale very quickly. GitLab was at par with GitHub for our future needs, but GitHub was a more familiar tool compared to GitLab. Bitbucket won out because of its close integration with Jira and being in the Atlassian family. It was also cheaper than GitHub. As we started with Jira, Bitbucket addition became a natural next step for us. We really liked Bitbucket and stayed with it but we do know we have great options in the form of GitHub and GitLab should we need to scale fast.