Need advice about which tool to choose?Ask the StackShare community!
Azure DevOps vs Azure DevOps Server: What are the differences?
What is Azure DevOps? Services for teams to share code, track work, and ship software. Azure DevOps provides unlimited private Git hosting, cloud build for continuous integration, agile planning, and release management for continuous delivery to the cloud and on-premises. Includes broad IDE support.
What is Azure DevOps Server? Collaborative software development tools for the entire team. It is set of collaborative software development tools, hosted on-premises. It integrates with your existing IDE or editor, enabling your cross-functional team to work effectively on projects of all sizes.
Azure DevOps and Azure DevOps Server are primarily classified as "Project Management" and "Integrated Development Environment" tools respectively.
Schlumberger, Poq, and simplement-e are some of the popular companies that use Azure DevOps, whereas Azure DevOps Server is used by IActionable, Attendee Events, and ParqEx. Azure DevOps has a broader approval, being mentioned in 79 company stacks & 68 developers stacks; compared to Azure DevOps Server, which is listed in 19 company stacks and 6 developer stacks.
Pros of Azure DevOps
- Complete and powerful51
- Huge extension ecosystem30
- Azure integration26
- One Stop Shop For Build server, Project Mgt, CDCI26
- Flexible and powerful25
- Everything I need. Simple and intuitive UI15
- Support Open Source13
- Integrations8
- GitHub Integration7
- Project Mgmt Features6
- Cost free for Stakeholders6
- One 4 all6
- Runs in the cloud5
- Crap5
- Agent On-Premise(Linux - Windows)3
- Aws integration2
- Link Test Cases to Stories2
- Jenkins Integration2
- GCP Integration1
Pros of Azure DevOps Server
- Affordable price, integration friendly, customization1
Sign up to add or upvote prosMake informed product decisions
Cons of Azure DevOps
- Still dependant on C# for agents7
- Half Baked4
- Not a requirements management tool4
- Capacity across cross functional teams not visibile4
- Jack of all trades, master of none3
- Poor Jenkins integration3
- Many in devops disregard MS altogether3
- Tedious for test plan/case creation2