Need advice about which tool to choose?Ask the StackShare community!
Azure DevOps vs Vagrant Cloud: What are the differences?
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; Vagrant Cloud: Share, discover, and create Vagrant environments. Vagrant Cloud pairs with Vagrant to enable access, insight and collaboration across teams, as well as to bring exposure to community contributions and development environments.
Azure DevOps and Vagrant Cloud are primarily classified as "Project Management" and "Virtual Machine Platforms & Containers" tools respectively.
Some of the features offered by Azure DevOps are:
- Agile Tools: kanban boards, backlogs, scrum boards
- Reporting: dashboards, widgets, Power BI
- Git: free private repositories, pull requests
On the other hand, Vagrant Cloud provides the following key features:
- Vagrant Share: A single command to share your local Vagrant environment to anyone in the world
- Box Distribution: Vagrant integration provides flexible versioning and support for private or community boxes
- Discover Boxes: Start new projects faster using the right box. Find trusted and top-used community boxes
Pros of Azure DevOps
- Complete and powerful56
- Huge extension ecosystem32
- Azure integration27
- Flexible and powerful26
- One Stop Shop For Build server, Project Mgt, CDCI26
- Everything I need. Simple and intuitive UI15
- Support Open Source13
- Integrations8
- GitHub Integration7
- Cost free for Stakeholders6
- One 4 all6
- Crap6
- Project Mgmt Features6
- Runs in the cloud5
- Agent On-Premise(Linux - Windows)3
- Aws integration2
- Link Test Cases to Stories2
- Jenkins Integration2
- GCP Integration1
Pros of Vagrant Cloud
- Well Known2
Sign up to add or upvote prosMake informed product decisions
Cons of Azure DevOps
- Still dependant on C# for agents8
- Half Baked5
- Many in devops disregard MS altogether5
- Not a requirements management tool4
- Jack of all trades, master of none4
- Capacity across cross functional teams not visibile4
- Poor Jenkins integration3
- Tedious for test plan/case creation2
- Switching accounts is impossible1