Need advice about which tool to choose?Ask the StackShare community!
Azure DevOps vs Bamboo: 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; Bamboo: Tie automated builds, tests, and releases together in a single workflow. Focus on coding and count on Bamboo as your CI and build server! Create multi-stage build plans, set up triggers to start builds upon commits, and assign agents to your critical builds and deployments.
Azure DevOps and Bamboo are primarily classified as "Project Management" and "Continuous Integration" tools respectively.
"Complete and powerful" is the top reason why over 11 developers like Azure DevOps, while over 7 developers mention "Integrates with other Atlassian tools" as the leading cause for choosing Bamboo.
According to the StackShare community, Azure DevOps has a broader approval, being mentioned in 79 company stacks & 68 developers stacks; compared to Bamboo, which is listed in 62 company stacks and 24 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 Bamboo
- Integrates with other Atlassian tools10
- Great notification scheme4
- Great UI2
- Has Deployment Projects1
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
Cons of Bamboo
- Expensive5