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 …
Bitbucket provides more features to version control and mange project sources. Build, test and deploy with integrated CI/CD. Benefit from configuration as code and fast feedback loops. Approve code review more efficiently with pull requests. Create a merge checklist with …
Bitbucket was inherited from an acquisition and not used by choice. The acquired company chose Bitbucket because - at the time - they were the market leader for private source code repositories and the team was already using JIRA.
We were using an older version of SVN when deciding to move away and buy Bitbucket. What we gained was: pull requests and code reviews, a nice UI, better permissions management and of course the JIRA/Bamboo integration, which made a huge impact on the software …
It's a relatively simple version control system so it works great for an individual or small team (less than 10 people). But if you have a medium to large team, especially one with members distributed over a large geographic area, or one where individuals need to be able to work "offline" without access to a central server, Apache Subversion will likely not be the best choice.
Also, if you're maintaining an open-source project where outside people will be interacting with your code repository, git is probably a better choice because it's becoming the de-facto standard these days and what most developers are familiar with.
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.
Distributed development - I've never worked in an environment where distributed development (developers widely scattered geographically) was a factor, but that's why git exists.
Merging - Merging of code from one branch to another can be painful, especially if it's not done frequently. (On the other hand, doing merges is one of the reasons I get a nice salary, so I can't complain too much!)
Acceptance - Let's face it, git is what "all the cool kids are using." If you've got a bunch of developers fresh out of school, they'll probably know git and not Subversion.
While there are interesting alternatives, such a GIT, Subversion has been a breath of fresh air compared to its predecessors like CVS or Microsoft Source Safe (now called Team Foundation Server). Its ease of use and high adoption rate is going to keep me using this product for years to come.
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.
Git has become the new standard of version control, with its support for distributed design. As a tool to manage and control versions, Subversion does it well, but Git is the future.
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.
