Rancher vs TeamCity: What are the differences?
Developers describe Rancher as "Open Source Platform for Running a Private Container Service". Rancher is an open source container management platform that includes full distributions of Kubernetes, Apache Mesos and Docker Swarm, and makes it simple to operate container clusters on any cloud or infrastructure platform. On the other hand, TeamCity is detailed as "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.
Rancher belongs to "Container Tools" category of the tech stack, while TeamCity can be primarily classified under "Continuous Integration".
Some of the features offered by Rancher are:
- Manage Hosts, Deploy Containers, Monitor Resources
- User Management & Collaboration
- Native Docker APIs & Tools
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
"Easy to use" is the top reason why over 89 developers like Rancher, while over 52 developers mention "Easy to configure" as the leading cause for choosing TeamCity.
Rancher is an open source tool with 11.8K GitHub stars and 1.31K GitHub forks. Here's a link to Rancher's open source repository on GitHub.
Stack Exchange, Yammer, and AX Semantics are some of the popular companies that use TeamCity, whereas Rancher is used by Packet, Redox Engine, and VCCloud. TeamCity has a broader approval, being mentioned in 168 company stacks & 51 developers stacks; compared to Rancher, which is listed in 88 company stacks and 35 developer stacks.
What is Rancher?
What is TeamCity?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
- Consume too much unnecessary resource by just running rancher agent alone;
- Hard to recover from system failure
- Bad performance of load balancing (compare to dokcer swarm built-in LB or others).
TeamCity is our main continuous integration server. It starts creating builds and running tests based on commits that we make in our hosted bitbucket repositories. From there, we have a set of configuraitons that can deploy the built and tested artifacts (web app, batches, db, etc...) to a stage or production server. We still release manually, but we release often, and TeamCity has nice features to help us roll back when things don't work out as planned.
TeamCity builds then copies to each web tier via a powershell script. The steps for each server are:
- Tell HAProxy to take the server out of rotation via a POST
- Delay to let IIS finish current requests (~5 sec)
- Stop the website (via the same PSSession for all the following)
- Robocopy files
- Start the website
- Re-enable in HAProxy via another POST
The whole infrastructure is managed through Rancher. It provides a simple interface to all the underlying tools - Docker, HAProxy (automatically configures load balancer from the containers).
I'm using a selfhosted TC as Referenceplatform, and use travis with another configuration.
Currently looking to move to Swarm or Kubernetes due to a few issues I have with Rancher.
Orchestration of containers for our environments. Remote deployment from Jenkins.
We use Rancher for container orchestration and automated deployment pipelines.