Knapsack Pro

Travis CI vs TeamCity comparison of Continuous Integration servers
What are the differences between Travis CI and TeamCity?

Travis CI

https://travis-ci.org

TeamCity

https://www.jetbrains.com/teamcity/
Unique feature

Build Matrix, ease of use, GitHub integration

Technology awareness

Type of product

SaaS, Self-hosted / On Premise

On Premise

Offers a free plan

Yes

Free for open source projects

Yes

They offer a great free professional plan, limited to 100 build configurations and 3 build agents. From there, you pay for each aditional agent you want (discounts if you purchase more than 1 agent at a time). They also provide a free plan for open source, non commercial projects, and steep 50% discounts for startups.

Predictable pricing

Yes

Clearly defined monthly plans, depending on concurrent jobs needed.

Yes

They have a clear list of prices per number of agents.

Support / SLA

Yes

Available via email, or dedicated online interface for paid plans.

Yes

Paralellism
Every CI servers tends to address this differently (parallel, distributed, build matrix). Some of it is just marketing, and some is just nuance. For this table, parallel means that tasks can be run concurrently on the same machine, distributed means that tasks can be scaled horizontally, on multiple machines
How to split tests in parallel in the optimal way with Knapsack Pro

Yes

TravisCI makes it very easy to split your build into different stages which are then run in parallel (ie: run integration tests separate from the unit tests). TravisCI calls this a build matrix: https://docs.travis-ci.com/user/build-matrix/. You can also very easily split tests accross several VMs using the knapsack_pro gem.

Yes

Distributed builds
distributed means that tasks can be scaled horizontally, on multiple machines
How to split tests in parallel in the optimal way with Knapsack Pro

N/A

N/A

No specific mention that we could find, but judging by the wording used it would appear that tasks can be divided accross different machines.

Containers support / Build environment

Yes

TravisCI runs each build in a isolated virtual machine. Pre-build packages include a few which support specific languages (Ruby and JavaScript included) or other software (Git, various databases), but vanilla packages such as Ubuntu Trusty are also available.

Yes

First class Docker support, among others

Analytics / Status overview
Analytics and overview referrs to the ability to, at a glance, see what's breaking (be it a certain task, or the build for a specific project)

Yes

Available by default in Travis (this is what most of the web UI consists of)

Yes

Great system overview, even allows building your own dashboards in order to see everything you're interested in at a glance.

Management support
How easy is it to manage users / projects / assign roles and permissions and so on

N/A

Yes

Allows assigning roles, LDAP and Windows domain integrations and more.

Self-hosted option

Yes

Yes

Hosted plans / SaaS

Yes

No

Build pipelines
A continuous delivery pipeline is a description of the process that the software goes through from a new code commit, through testing and other statical analysis steps all the way to the end-users of the product.

No

Specifically built around GitHub pull requests. Pipelines can be defined, but parts of the process need to be implemented separatelly in GitHub.

Yes

Unlike most options in the CI/CD space, TeamCity allows defining pipelines using a Kotlin-based DSL. This unlocks a lot of potential, such as templates for common CI/CD tasks, and deep integration with various IDEs (not just JetBrains IDEs)

Reports
Reports are about the abilty to see specific reports (like code coverage or custom ones), but not necesarily tied in into a larger dashboard.

Yes (partial)

No persistent storage eliminates the possibility of code coverage reports on TravisCI alone. There is support for integrated 3rd parties such as Coveralls for reporting code coverage.

Yes

Something that stands out from the rest, allows integrating third party reports, as long as they produce HTML output.

Ecosystem
Besides the official documentation and software, is there a large community using this product? Are there any community-driven tools / plugins that you can use?

No plugin support in TravisCI, plugins for other tools

Yes

JetBrains has a rich ecosystem of plugins in general.

Specific language support: Ruby
Some CI servers have built-in support for parsing RSpec or Istanbul output for example and we mention those. Some others make it even easier by detecting Gemfiles or package.json and automate parts of the process for the developer.

Yes

TravisCI is designed to be a simple way to integrate CI/CD in your workflow so it has a couple of features aimed at specific languages, such as Ruby, starting from pre-built containers (with RVM already installed, for example) all the way to automatically running specific platform commands (such as detecting a Gemfile in the root of the project and automatically bundling dependencies). TravisCI also builds a Ruby SDK for easier use of the API.

Yes

Using what they call 'Technology Awareness', promises great intehration with Ruby projects, with features such as testing framework support, static analysis and code coverage available out of the box, with no additional work required: https://www.jetbrains.com/teamcity/features/technology_awareness.html

Specific language support: JavaScript

Yes

TravisCI is designed to be a simple way to integrate CI/CD in your workflow so it has a couple of features aimed at specific languages, such as Javascript, starting from pre-built containers (with node already installed, for example) all the way to automatically running specific platform commands (such as detecting a package.json in the root of the project and running npm test)

No (partial)

Unlike Ruby, there's no first class support for Javascript, although they do advertise the fact that their large collections of plugins can cover any use case for Javascript projects: https://plugins.jetbrains.com/teamcity

Integrations
1st party support for common tools (like Slack notifications, various VCS platforms, etc)

Yes

By default, TravisCI is built to work with GitHub. Additionally, there is strong support for 3rd party tools like Coveralls, BrowserStack, etc.

Yes

Great cloud integrations (Google Cloud, AWS, VMWare, etc) as well as 'key' integrations (VSCode, Jira, even NuGet)

API
Custom integreation is available, via an API or otherwise, it's mentioned separately as it allows further customization than any of the Ecosystem/Integration options

Yes

Offers a feature-rich API that allows both reading data, as well as triggering or cancelling builds.

Yes

Unlike most tools, which offer just a Rest API, TeamCity provides ample opportunity for extension via plugins, their own API, and service messages (formatted messages on stdout)

Auditing

N/A

Yes

Additional notes

Great ecosystem, with a strong focus on integration with other tools (not only JetBrains).

Travis CI build matrix feature how to use it for CI parallelisation

Travis CI parallelism integration

Start using Knapsack Pro with Travis CI or TeamCity

Sign up and speed up your tests.

Get started free