Need advice about which tool to choose?Ask the StackShare community!
Ansible vs TeamCity: What are the differences?
What is Ansible? Radically simple configuration-management, application deployment, task-execution, and multi-node orchestration engine. Ansible is an IT automation tool. It can configure systems, deploy software, and orchestrate more advanced IT tasks such as continuous deployments or zero downtime rolling updates. Ansible’s goals are foremost those of simplicity and maximum ease of use.
What is 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.
Ansible can be classified as a tool in the "Server Configuration and Automation" category, while TeamCity is grouped under "Continuous Integration".
Some of the features offered by Ansible are:
- Ansible's natural automation language allows sysadmins, developers, and IT managers to complete automation projects in hours, not weeks.
- Ansible uses SSH by default instead of requiring agents everywhere. Avoid extra open ports, improve security, eliminate "managing the management", and reclaim CPU cycles.
- Ansible automates app deployment, configuration management, workflow orchestration, and even cloud provisioning all from one system.
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
"Agentless" is the primary reason why developers consider Ansible over the competitors, whereas "Easy to configure" was stated as the key factor in picking TeamCity.
Ansible is an open source tool with 37.8K GitHub stars and 15.8K GitHub forks. Here's a link to Ansible's open source repository on GitHub.
According to the StackShare community, Ansible has a broader approval, being mentioned in 955 company stacks & 578 developers stacks; compared to TeamCity, which is listed in 168 company stacks and 51 developer stacks.
I'm just getting started using Vagrant to help automate setting up local VMs to set up a Kubernetes cluster (development and experimentation only). (Yes, I do know about minikube)
I'm looking for a tool to help install software packages, setup users, etc..., on these VMs. I'm also fairly new to Ansible, Chef, and Puppet. What's a good one to start with to learn? I might decide to try all 3 at some point for my own curiosity.
The most important factors for me are simplicity, ease of use, shortest learning curve.
AnsibleI have been working with Puppet and Ansible. The reason why I prefer ansible is the distribution of it. Ansible is more lightweight and therefore more popular. This leads to situations, where you can get fully packaged applications for ansible (e.g. confluent) supported by the vendor, but only incomplete packages for Puppet.
The only advantage I would see with Puppet if someone wants to use Foreman. This is still better supported with Puppet.
If you are just starting out, might as well learn Kubernetes There's a lot of tools that come with Kube that make it easier to use and most importantly: you become cloud-agnostic. We use Ansible because it's a lot simpler than Chef or Puppet and if you use Docker Compose for your deployments you can re-use them with Kubernetes later when you migrate
Pros of Ansible
- Agentless276
- Great configuration204
- Simple195
- Powerful173
- Easy to learn151
- Flexible66
- Doesn't get in the way of getting s--- done54
- Makes sense34
- Super efficient and flexible29
- Powerful27
- Dynamic Inventory11
- Backed by Red Hat8
- Works with AWS7
- Cloud Oriented6
- Easy to maintain6
- Because SSH4
- Multi language4
- Easy4
- Simple4
- Procedural or declarative, or both4
- Simple and powerful4
- Consistency3
- Vagrant provisioner3
- Fast as hell2
- Masterless2
- Well-documented2
- Merge hash to get final configuration similar to hiera2
- Debugging is simple2
- Work on windows, but difficult to manage1
- Certified Content1
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 Ansible
- Dangerous5
- Hard to install5
- Bloated3
- Backward compatibility3
- Doesn't Run on Windows2
- No immutable infrastructure2
Cons of TeamCity
- User friendly2
- Proprietary1
- High costs for more than three build agents1
- User-friendly1
Sign up to add or upvote consMake informed product decisions
What is Ansible?
What is TeamCity?
Need advice about which tool to choose?Ask the StackShare community!
What companies use Ansible?
What companies use TeamCity?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Ansible?
What tools integrate with TeamCity?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+14
+13
+22+46+30
+33
+23+42