Get Advice Icon

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

Capistrano
Capistrano

856
471
+ 1
232
TeamCity
TeamCity

645
427
+ 1
290
Add tool

Capistrano vs TeamCity: What are the differences?

What is Capistrano? A remote server automation and deployment tool written in Ruby. Capistrano is a remote server automation tool. It supports the scripting and execution of arbitrary tasks, and includes a set of sane-default deployment workflows.

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.

Capistrano belongs to "Server Configuration and Automation" category of the tech stack, while TeamCity can be primarily classified under "Continuous Integration".

Some of the features offered by Capistrano are:

  • Reliably deploy web application to any number of machines simultaneously, in sequence or as a rolling set
  • Automate audits of any number of machines (checking login logs, enumerating uptimes, and/or applying security patches)
  • Script arbitrary workflows over SSH

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

"Automated deployment with several custom recipes" is the top reason why over 122 developers like Capistrano, while over 52 developers mention "Easy to configure" as the leading cause for choosing TeamCity.

Capistrano is an open source tool with 11.1K GitHub stars and 1.72K GitHub forks. Here's a link to Capistrano's open source repository on GitHub.

Tilt, Gauges, and New Relic are some of the popular companies that use Capistrano, whereas TeamCity is used by ebay, Apple, and Intuit. Capistrano has a broader approval, being mentioned in 295 company stacks & 81 developers stacks; compared to TeamCity, which is listed in 168 company stacks and 51 developer stacks.

- No public GitHub repository available -

What is Capistrano?

Capistrano is a remote server automation tool. It supports the scripting and execution of arbitrary tasks, and includes a set of sane-default deployment workflows.

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.
Get Advice Icon

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

Why do developers choose Capistrano?
Why do developers choose TeamCity?

Sign up to add, upvote and see more prosMake informed product decisions

    Be the first to leave a con
    Jobs that mention Capistrano and TeamCity as a desired skillset
    What companies use Capistrano?
    What companies use TeamCity?

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with Capistrano?
    What tools integrate with TeamCity?

    Sign up to get full access to all the tool integrationsMake informed product decisions

    What are some alternatives to Capistrano and TeamCity?
    Fabric
    Fabric is a Python (2.5-2.7) library and command-line tool for streamlining the use of SSH for application deployment or systems administration tasks. It provides a basic suite of operations for executing local or remote shell commands (normally or via sudo) and uploading/downloading files, as well as auxiliary functionality such as prompting the running user for input, or aborting execution.
    Shipit
    Shipit is an automation engine and a deployment tool written for node / iojs. Shipit was built to be a Capistrano alternative for people who don't know ruby, or who experienced some issues with it. If you want to write tasks in JavaScript and enjoy the node ecosystem, Shipit is also for you.
    Docker
    The Docker Platform is the industry-leading container platform for continuous, high-velocity innovation, enabling organizations to seamlessly build and share any application — from legacy to what comes next — and securely run them anywhere
    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.
    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.
    See all alternatives
    Decisions about Capistrano and TeamCity
    Kir Shatrov
    Kir Shatrov
    Production Engineer at Shopify · | 13 upvotes · 27.9K views
    atShopifyShopify
    kubernetes-deploy
    kubernetes-deploy
    Capistrano
    Capistrano
    Heroku
    Heroku
    Shipit
    Shipit
    #BuildTestDeploy
    #ContainerTools
    #ApplicationHosting
    #PlatformAsAService

    Shipit, our deployment tool, is at the heart of Continuous Delivery at Shopify. Shipit is an orchestrator that runs and tracks progress of any deploy script that you provide for a project. It supports deploying to Rubygems, Pip, Heroku and Capistrano out of the box. For us, it's mostly kubernetes-deploy or Capistrano for legacy projects.

    We use a slightly tweaked GitHub flow, with feature development going in branches and the master branch being the source of truth for the state of things in production. When your PR is ready, you add it to the Merge Queue in ShipIt. The idea behind the Merge Queue is to control the rate of code that is being merged to master branch. In the busy hours, we have many developers who want to merge the PRs, but at the same time we don't want to introduce too many changes to the system at the same time. Merge Queue limits deploys to 5-10 commits at a time, which makes it easier to identify issues and roll back in case we notice any unexpected behaviour after the deploy.

    We use a browser extension to make Merge Queue play nicely with the Merge button on GitHub:

    Both Shipit and kubernetes-deploy are open source, and we've heard quite a few success stories from companies who have adopted our flow.

    #BuildTestDeploy #ContainerTools #ApplicationHosting #PlatformAsAService

    See more
    Tymoteusz Paul
    Tymoteusz Paul
    Devops guy at X20X Development LTD · | 13 upvotes · 294K views
    Amazon EC2
    Amazon EC2
    LXC
    LXC
    CircleCI
    CircleCI
    Docker
    Docker
    Git
    Git
    Vault
    Vault
    Apache Maven
    Apache Maven
    Slack
    Slack
    Jenkins
    Jenkins
    TeamCity
    TeamCity
    Logstash
    Logstash
    Kibana
    Kibana
    Elasticsearch
    Elasticsearch
    Ansible
    Ansible
    VirtualBox
    VirtualBox
    Vagrant
    Vagrant

    Often enough I have to explain my way of going about setting up a CI/CD pipeline with multiple deployment platforms. Since I am a bit tired of yapping the same every single time, I've decided to write it up and share with the world this way, and send people to read it instead ;). I will explain it on "live-example" of how the Rome got built, basing that current methodology exists only of readme.md and wishes of good luck (as it usually is ;)).

    It always starts with an app, whatever it may be and reading the readmes available while Vagrant and VirtualBox is installing and updating. Following that is the first hurdle to go over - convert all the instruction/scripts into Ansible playbook(s), and only stopping when doing a clear vagrant up or vagrant reload we will have a fully working environment. As our Vagrant environment is now functional, it's time to break it! This is the moment to look for how things can be done better (too rigid/too lose versioning? Sloppy environment setup?) and replace them with the right way to do stuff, one that won't bite us in the backside. This is the point, and the best opportunity, to upcycle the existing way of doing dev environment to produce a proper, production-grade product.

    I should probably digress here for a moment and explain why. I firmly believe that the way you deploy production is the same way you should deploy develop, shy of few debugging-friendly setting. This way you avoid the discrepancy between how production work vs how development works, which almost always causes major pains in the back of the neck, and with use of proper tools should mean no more work for the developers. That's why we start with Vagrant as developer boxes should be as easy as vagrant up, but the meat of our product lies in Ansible which will do meat of the work and can be applied to almost anything: AWS, bare metal, docker, LXC, in open net, behind vpn - you name it.

    We must also give proper consideration to monitoring and logging hoovering at this point. My generic answer here is to grab Elasticsearch, Kibana, and Logstash. While for different use cases there may be better solutions, this one is well battle-tested, performs reasonably and is very easy to scale both vertically (within some limits) and horizontally. Logstash rules are easy to write and are well supported in maintenance through Ansible, which as I've mentioned earlier, are at the very core of things, and creating triggers/reports and alerts based on Elastic and Kibana is generally a breeze, including some quite complex aggregations.

    If we are happy with the state of the Ansible it's time to move on and put all those roles and playbooks to work. Namely, we need something to manage our CI/CD pipelines. For me, the choice is obvious: TeamCity. It's modern, robust and unlike most of the light-weight alternatives, it's transparent. What I mean by that is that it doesn't tell you how to do things, doesn't limit your ways to deploy, or test, or package for that matter. Instead, it provides a developer-friendly and rich playground for your pipelines. You can do most the same with Jenkins, but it has a quite dated look and feel to it, while also missing some key functionality that must be brought in via plugins (like quality REST API which comes built-in with TeamCity). It also comes with all the common-handy plugins like Slack or Apache Maven integration.

    The exact flow between CI and CD varies too greatly from one application to another to describe, so I will outline a few rules that guide me in it: 1. Make build steps as small as possible. This way when something breaks, we know exactly where, without needing to dig and root around. 2. All security credentials besides development environment must be sources from individual Vault instances. Keys to those containers should exist only on the CI/CD box and accessible by a few people (the less the better). This is pretty self-explanatory, as anything besides dev may contain sensitive data and, at times, be public-facing. Because of that appropriate security must be present. TeamCity shines in this department with excellent secrets-management. 3. Every part of the build chain shall consume and produce artifacts. If it creates nothing, it likely shouldn't be its own build. This way if any issue shows up with any environment or version, all developer has to do it is grab appropriate artifacts to reproduce the issue locally. 4. Deployment builds should be directly tied to specific Git branches/tags. This enables much easier tracking of what caused an issue, including automated identifying and tagging the author (nothing like automated regression testing!).

    Speaking of deployments, I generally try to keep it simple but also with a close eye on the wallet. Because of that, I am more than happy with AWS or another cloud provider, but also constantly peeking at the loads and do we get the value of what we are paying for. Often enough the pattern of use is not constantly erratic, but rather has a firm baseline which could be migrated away from the cloud and into bare metal boxes. That is another part where this approach strongly triumphs over the common Docker and CircleCI setup, where you are very much tied in to use cloud providers and getting out is expensive. Here to embrace bare-metal hosting all you need is a help of some container-based self-hosting software, my personal preference is with Proxmox and LXC. Following that all you must write are ansible scripts to manage hardware of Proxmox, similar way as you do for Amazon EC2 (ansible supports both greatly) and you are good to go. One does not exclude another, quite the opposite, as they can live in great synergy and cut your costs dramatically (the heavier your base load, the bigger the savings) while providing production-grade resiliency.

    See more
    Interest over time
    Reviews of Capistrano and TeamCity
    No reviews found
    How developers use Capistrano and TeamCity
    Avatar of DigitalPermits
    DigitalPermits uses TeamCityTeamCity

    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.

    Avatar of Stack Exchange
    Stack Exchange uses TeamCityTeamCity

    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
    Avatar of Cyrus Stoller
    Cyrus Stoller uses CapistranoCapistrano

    For deploying to a VPS like DigitalOcean. This pairs nicely with https://github.com/cyrusstoller/gardenbed.

    Avatar of Sascha Manns
    Sascha Manns uses TeamCityTeamCity

    I'm using a selfhosted TC as Referenceplatform, and use travis with another configuration.

    Avatar of GeniusLink
    GeniusLink uses CapistranoCapistrano

    Deployment automation all of the websites and apps are deployed to linux via capistrano.

    Avatar of Nick De Cooman
    Nick De Cooman uses CapistranoCapistrano

    Before Docker, I used Capistrano to deploy all web projects.

    Avatar of douglasresende
    douglasresende uses CapistranoCapistrano

    I use do make deploy my applications into many servers.

    Avatar of Cyril Duchon-Doris
    Cyril Duchon-Doris uses CapistranoCapistrano

    Deployment to remote AWS auto-scaled infrastructure.

    Avatar of Andrew King
    Andrew King uses TeamCityTeamCity

    Continuous integration for iOS apps.

    Avatar of One Legal
    One Legal uses TeamCityTeamCity

    Build system.

    How much does Capistrano cost?
    How much does TeamCity cost?
    Pricing unavailable
    News about Capistrano
    More news