Need advice about which tool to choose?Ask the StackShare community!

Ansible

14K
11.1K
+ 1
1.3K
TeamCity

1K
913
+ 1
307
Add tool

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.

Advice on Ansible and TeamCity
Needs advice
on
Puppet LabsPuppet LabsChefChef
and
AnsibleAnsible

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.

See more
Replies (2)
Recommends
AnsibleAnsible

I 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.

See more
Gabriel Pa
Recommends
KubernetesKubernetes
at

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

See more
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Ansible
Pros of TeamCity
  • 276
    Agentless
  • 204
    Great configuration
  • 195
    Simple
  • 173
    Powerful
  • 151
    Easy to learn
  • 66
    Flexible
  • 54
    Doesn't get in the way of getting s--- done
  • 34
    Makes sense
  • 29
    Super efficient and flexible
  • 27
    Powerful
  • 11
    Dynamic Inventory
  • 8
    Backed by Red Hat
  • 7
    Works with AWS
  • 6
    Cloud Oriented
  • 6
    Easy to maintain
  • 4
    Because SSH
  • 4
    Multi language
  • 4
    Easy
  • 4
    Simple
  • 4
    Procedural or declarative, or both
  • 4
    Simple and powerful
  • 3
    Consistency
  • 3
    Vagrant provisioner
  • 2
    Fast as hell
  • 2
    Masterless
  • 2
    Well-documented
  • 2
    Merge hash to get final configuration similar to hiera
  • 2
    Debugging is simple
  • 1
    Work on windows, but difficult to manage
  • 1
    Certified Content
  • 60
    Easy to configure
  • 37
    Reliable and high-quality
  • 31
    User friendly
  • 31
    Github integration
  • 31
    On premise
  • 18
    Great UI
  • 16
    Smart
  • 12
    Free for open source
  • 12
    Can run jobs in parallel
  • 8
    Crossplatform
  • 4
    REST API
  • 4
    Great support by jetbrains
  • 4
    Fully-functional out of the box
  • 4
    Projects hierarchy
  • 4
    Chain dependencies
  • 3
    100+ plugins
  • 3
    Free for small teams
  • 3
    Per-project permissions
  • 3
    Personal notifications
  • 3
    Build templates
  • 2
    Ide plugins
  • 2
    GitLab integration
  • 2
    Smart build failure analysis and tracking
  • 2
    Upload build artifacts
  • 2
    Artifact dependencies
  • 2
    Build progress messages promoting from running process
  • 1
    TeamCity Professional is FREE
  • 1
    Powerful build chains / pipelines
  • 1
    Built-in artifacts repository
  • 1
    Repository-stored, full settings dsl with ide support
  • 0
    Official reliable support
  • 0
    High-Availability
  • 0
    Hosted internally

Sign up to add or upvote prosMake informed product decisions

Cons of Ansible
Cons of TeamCity
  • 5
    Dangerous
  • 5
    Hard to install
  • 3
    Bloated
  • 3
    Backward compatibility
  • 2
    Doesn't Run on Windows
  • 2
    No immutable infrastructure
  • 2
    User friendly
  • 1
    Proprietary
  • 1
    High costs for more than three build agents
  • 1
    User-friendly

Sign up to add or upvote consMake informed product decisions

- No public GitHub repository available -

What is Ansible?

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 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.

Need advice about which tool to choose?Ask the StackShare community!

What companies use Ansible?
What companies use TeamCity?
See which teams inside your own company are using Ansible or TeamCity.
Sign up for Private StackShareLearn More

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

PythonDockerKubernetes+14
11
2108
GitHubGitSlack+30
25
15538
JavaScriptGitHubGit+33
20
1718
GitHubDockerAmazon EC2+23
12
6360
JavaScriptGitHubPython+42
52
19902
What are some alternatives to Ansible and TeamCity?
Puppet Labs
Puppet is an automated administrative engine for your Linux, Unix, and Windows systems and performs administrative tasks (such as adding users, installing packages, and updating server configurations) based on a centralized specification.
Chef
Chef enables you to manage and scale cloud infrastructure with no downtime or interruptions. Freely move applications and configurations from one cloud to another. Chef is integrated with all major cloud providers including Amazon EC2, VMWare, IBM Smartcloud, Rackspace, OpenStack, Windows Azure, HP Cloud, Google Compute Engine, Joyent Cloud and others.
Salt
Salt is a new approach to infrastructure management. Easy enough to get running in minutes, scalable enough to manage tens of thousands of servers, and fast enough to communicate with them in seconds. Salt delivers a dynamic communication bus for infrastructures that can be used for orchestration, remote execution, configuration management and much more.
Terraform
With Terraform, you describe your complete infrastructure as code, even as it spans multiple service providers. Your servers may come from AWS, your DNS may come from CloudFlare, and your database may come from Heroku. Terraform will build all these resources across all these providers in parallel.
Jenkins
In a nutshell Jenkins CI is the leading open-source continuous integration server. Built with Java, it provides over 300 plugins to support building and testing virtually any project.
See all alternatives