Bitbucket is a Git repository and code collaboration platform, featuring automated testing and code deployment. Bitbucket Cloud Premium provides AI-powered development, more granular access controls, and enforced code quality, and Bitbucket Data Center provides a self-hosted option.
$0
Azure DevOps
Score 8.2 out of 10
N/A
Azure DevOps (formerly VSTS, Microsoft Visual Studio Team System) is an agile development product that is an extension of the Microsoft Visual Studio architecture. Azure DevOps includes software development, collaboration, and reporting capabilities.
$2
per GB (first 2GB free)
Azure DevOps Server
Score 8.4 out of 10
N/A
Azure DevOps Server (formerly Team Foundation Server, or TFS) is the on-premise version of Azure DevOps. To license Azure DevOps Server an Azure DevOps license and a Windows operating system license (e.g. Windows Server) for each machine running Azure DevOps Server.
N/A
Pricing
Atlassian Bitbucket
Azure DevOps
Azure DevOps Server
Editions & Modules
Free
$0
for up to 5 users
Standard
$3.30
per month per user
Premium
$6.60
per month per user
Bitbucket Data Center
starting at $44,000
per year 1 - 500
Azure Artifacts
$2
per GB (first 2GB free)
Basic Plan
$6
per user per month (first 5 users free)
Azure Pipelines - Self-Hosted
$15
per extra parallel job (1 free parallel job with unlimited minutes)
Azure Pipelines - Microsoft Hosted
$40
per parallel job (1,800 minutes free with 1 free parallel job)
The majority of SCM tools are Git based. What makes this solution stand out from the rest is it's web-based interface, which implements version control standards very intuitively. As a result, the learning curve shortens and productivity is highly improved.
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 …
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.
The primary reasons we went with Bitbucket over TFS and/or other options are as follows: 1) Ability to integrate with other documentation and development tools we were using. 2) Cost - with our size and current business needs, we were able to implement what we needed in …
Drastically simpler both in pricing and ease of use than the competition. For only $10/month your team has unlimited private repos! That is an outright bargain! If you are a small team that doesn't require all of the advanced services that come with larger infrastructure and …
Currently, we use both products, however, we use more the Atlassian suite. We have started recently using Azure DevOps for specific implementations and projects. We don't have any plan yet to migrate all our projects to Azure DevOps, we may in the next couple of years. …
Beside all cloud benefits, the main advantage Azure DevOps Services compared to Azure DevOps Server is the easier remote access for third party team members, and always up to date software. On the other hand, on prem deployment (Azure DevOps Server) makes complex access or …
I prefer Azure Devops over all other code repository / ci/cd systems that I've used in the past. All features are integrated into a single service (back log, repo mgmt, deployment pipelines, artifacts, etc.). The tools are easy to use and super powerful.
While GitLab has the same features as Azure DevOps, and a potentially more competitive price, its project management features are a bit more primitive. It could be helpful for small projects, but ultimately for our larger projects we went with Azure DevOps. Bitbucket has good …
Azure DevOps required the least amount of up front knowledge to get a pipeline up and running. Because of the built in activities, when I initially started working with this tool I didn't have to know anything other than where my code was stored. The rest was easy enough to …
If you are currently using Jenkins or Bitbucket as an ALM tool, then I would highly recommend taking a look at Azure DevOps as the integration to the Microsoft stack is extremely easy and versatile. Microsoft has invested heavily in getting this tool best in class with the …
Compared to other tools we have used, Microsoft STS has been a much more complete tool. Communication, collaboration, tracking, management, automation, testing, speed to production—all these areas have been improved since we started using Microsoft STS. We have been looking for …
Our TFS was dated and in some ways was quite crude. VSTS is thoroughly modern and I don't have to worry about updating it since MS is always updating VSTS. Also, VSTS has better integration with other products such as JIRA than our older TFS would. I am sure you could integrate …
Being its predecessor, VSS has a very limited team-sharing view, providing little to no multiple-user, multiple-project support. Considering the fact that Microsoft has purged its support in favor of TFS and VSTS, it's only reasonable to believe they have something extra. Git …
Haven't used a lot of similar products that have the full feature set as Visual Studio. It's highly effective development platform especially when used with SVN and TFS makes large Agile project easy to manage and collaborate.
I haven't used any other products, so I can't say how VSTS/TFS would stack against any competitors, but I know that for an SDLC management tool, VSTS/TFS has everything you need to help an organization meet the requirements needed to adhere to the specific/general practices …
Azure DevOps is a fully integrated solution that solves all of the problems that our separate tools did in a much easier-to-use way. Before we implemented DevOps we had three different solutions that we had to integrate with each other and required a lot of manual intervention …
The advantage of Team Foundation Server is the integration capability with Microsoft technologies and products, such as Visual Studio. Although this is an important consideration, Team Foundation Server is not a straightforward tool and needs to be improved to work seamlessly …
The JIRA integration with Bitbucket is a little nicer for sure, since they're both Atlassian products. Still, the Visual Studio and Azure integration with TFS made this a no-brainer for me.
Price-wise they are similar but you get a lot more with your TFS subscription. For the …
Based on the fact we are Microsoft shop, it makes sense and it has an great integration to RM for code release. At the time it was the best decision for what we needed as a team. If it were up to me, moving to Git would be the right direction. It is less costly and it is …
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.
Azure DevOps works well when you’ve got larger delivery efforts with multiple teams and a lot of moving parts, and you need one place to plan work, track it properly, and see how everything links together. It’s especially useful when delivery and development are closely tied and you want backlog items, code and releases connected rather than spread across tools. Where it’s less of a fit is for small teams or simple pieces of work, as it can feel like more setup and process than you really need, and non-technical users often struggle with the interface. It also isn’t great if you want instant, easy programme-level views or a very visual planning experience without putting time into configuration.
Azure DevOps is good to use if you are all-in on the Microsoft Azure stack. It's fully integrated across Azure so it is a point-and-click for most of what you will need to achieve. If you are new to Azure make sure you get some outside experience to help you otherwise it is very easy to overcomplicate things and go down the wrong track, or for you to manually create things that come out of the box.
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.
I did mention it has good visibility in terms of linking, but sometimes items do get lost, so if there was a better way to manage that, that would be great.
The wiki is not the prettiest thing to look at, so it could have refinements there.
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.
I don't think our organization will stray from using VSTS/TFS as we are now looking to upgrade to the 2012 version. Since our business is software development and we want to meet the requirements of CMMI to deliver consistent and high quality software, this SDLC management tool is here to stay. In addition, our company uses a lot of Microsoft products, such as Office 365, Asp.net, etc, and since VSTS/TFS has proved itself invaluable to our own processes and is within the Microsoft family of products, we will continue to use VSTS/TFS for a long, long time.
Because we are a Microsoft Gold Partner we utilize most of their software and we have so much invested in Team Foundation Server now it would take a catastrophic amount of time and resources to switch to a different 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.
It's a great help to get more information about new feature release and stay updated on what the dev team is working on. I like how easy it is to just login and read through the work items. Each work item has basic details: Title, Description, Assigned to, State, Area (what it belongs to), and iteration (when it’s worked on). See image above.They move through different states (New → Discovery → Ready for Prod → etc.).
For standard users the interface is friendly. but if you are a manager some tools are a little confusing to use, like the query system that you always need to create from scratch. Templates should be more helpful for queries and for standard procedures that you need to duplicate PBIs over time. The search history of Work Items is a little painful to use.
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.
When we've had issues, both Microsoft support and the user community have been very responsive. DevOps has an active developer community and frankly, you can find most of your questions already asked and answered there. Microsoft also does a better job than most software vendors I've worked with creating detailed and frequently updated documentation.
I have not had to use the support for Azure DevOps Server. There have never been any issues where I was not able to figure it out or quickly resolve. Our Scrum Master has used support before though, and the service has always been prompt and clear with a customer-focus
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.
Microsoft Planner is used by project managers and IT service managers across our organization for task tracking and running their team meetings. Azure DevOps works better than Planner for software development teams but might possibly be too complex for non-software teams or more business-focused projects. We also use ServiceNow for IT service management and this tool provides better analysis and tracking of IT incidents, as Azure DevOps is more suited to development and project work for dev teams.
In my opinion, DevOps covers the development process end to end way better than Jira or GitHub. Both competitors are nice in their specific fields but DevOps provides a more comprehensive package in my opinion. It is still crazy to see that the whole suite can be used for free. The productivity increase we realized with DevOps is worth real money!
We have saved a ton of time not calculating metrics by hand.
We no longer spend time writing out cards during planning, it goes straight to the board.
We no longer track separate documents to track overall department goals. We were able to create customized icons at the department level that lets us track each team's progress against our dept goals.
It has streamlined the pipeline and project management for our agile effort.
It has helped our agile team get organized since that is a new methodology being leveraged within the Enterprise.
The calendar has improved visibility into different OOOs across the project team since we all come from different departments across the larger organization.