Need advice about which tool to choose?Ask the StackShare community!
Azure DevOps vs TeamCity: 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; TeamCity: TeamCity is an ultimate Continuous Integration tool for professionals. TeamCity is a user-friendly continuous integration (CI) server for professional developers, build engineers, and DevOps. It is trivial to setup and absolutely free for small teams and open source projects.
Azure DevOps belongs to "Integrated Development Environment Tools" category of the tech stack, while TeamCity can be primarily classified under "Continuous Integration".
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, TeamCity provides the following key features:
- Automate code analyzing, compiling, and testing processes, with having instant feedback on build progress, problems, and test failures, all in a simple, intuitive web-interface
- Simplified setup: create projects from just a VCS repository URL
- Run multiple builds and tests under different configurations and platforms simultaneously
"Complete and powerful" is the primary reason why developers consider Azure DevOps over the competitors, whereas "Easy to configure" was stated as the key factor in picking TeamCity.
According to the StackShare community, TeamCity has a broader approval, being mentioned in 168 company stacks & 51 developers stacks; compared to Azure DevOps, which is listed in 69 company stacks and 65 developer stacks.
Pros of Azure DevOps
- Complete and powerful49
- Huge extension ecosystem29
- Azure integration26
- One Stop Shop For Build server, Project Mgt, CDCI25
- Flexible and powerful25
- Everything I need. Simple and intuitive UI15
- Support Open Source13
- Integrations8
- GitHub Integration7
- One 4 all6
- Project Mgmt Features6
- Crap5
- Runs in the cloud5
- Cost free for Stakeholders5
- Agent On-Premise(Linux - Windows)3
- Aws integration2
- Jenkins Integration2
- GCP Integration1
Pros of TeamCity
- Easy to configure60
- Reliable and high-quality37
- User friendly31
- Github integration31
- On premise31
- Great UI18
- Smart16
- Free for open source12
- Can run jobs in parallel12
- Crossplatform8
- REST API4
- Great support by jetbrains4
- Fully-functional out of the box4
- Projects hierarchy4
- Chain dependencies4
- 100+ plugins3
- Free for small teams3
- Per-project permissions3
- Personal notifications3
- Build templates3
- Ide plugins2
- GitLab integration2
- Smart build failure analysis and tracking2
- Upload build artifacts2
- Artifact dependencies2
- Build progress messages promoting from running process2
- TeamCity Professional is FREE1
- Powerful build chains / pipelines1
- Built-in artifacts repository1
- Repository-stored, full settings dsl with ide support1
- Official reliable support0
- High-Availability0
- Hosted internally0
Sign up to add or upvote prosMake informed product decisions
Cons of Azure DevOps
- Still dependant on C# for agents6
- Capacity across cross functional teams not visibile4
- Half Baked4
- Not a requirements management tool3
- Poor Jenkins integration3
- Many in devops disregard MS altogether3
- Jack of all trades, master of none3
Cons of TeamCity
- Proprietary1
- High costs for more than three build agents1
- User friendly1
- User-friendly1