Knapsack Pro

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

Travis CI

https://travis-ci.org

Jenkins

https://jenkins.io
Unique feature

Build Matrix, ease of use, GitHub integration

Plugins

Type of product

SaaS, Self-hosted / On Premise

Self-hosted / On Premise

Offers a free plan

Yes

Free for open source projects

Yes

Free, open source software
Predictable pricing

Yes

Clearly defined monthly plans, depending on concurrent jobs needed.

Yes

Jenkins is free software, the only costs are those assigned to running your infrastructure.
Support / SLA

Yes

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

No (partial)

No official support available, or SLAs. However, Jenkins' popularity ensures you'll find support in various places (official Jenkins forum, IRC, StackOverflow etc.)
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 (partial)

Jenkins allows builds to be run in parallel, but all builds share the same environment and there can be issues arising from shared resources such as the filesystem.
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

Yes (partial)

Jenkins has a concept of master server and agents, for distributing builds, but setting that up requires quite a bit of manual work from a sysadmin, compared to other options.
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.

No (partial)

By default, Jenkins runs all builds in the same environment as the build server itself, which can lead to numerous issues and is generally not a good practice. Some plugins address this issue, but they need to be manually installed.
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

Available via the Blue Ocean project (part of Jenkins): https://jenkins.io/doc/book/blueocean/dashboard/#dashboard
Management support
How easy is it to manage users / projects / assign roles and permissions and so on

N/A

No

In practice, for Jenkins it usually means that there's someone solely in charge of the Jenkins instance (configuration, management). Collaboration features built into other similar products are lacking, as are governance features (no easy way to tell from Jenkins alone _who_ is responsabile for a broken build, for example), even if your Version Control Server of choice can give that information (via `git blame` for example).
Self-hosted option

Yes

Yes

Jenkins is Open Source Software, and self-hosting is the only way to use it.
Hosted plans / SaaS

Yes

No

Only available for self-hosting.
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

Offers extensive support for custom pipelines, either through the Jenkins Pipeline DSL, written in a Jenkinsfile, either through the Web UI. Also, their Blue Ocean project is a great tool for building pipelines: https://jenkins.io/projects/blueocean/
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

Has ready-made integrations for standard reports such as JUnit test results.
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

> 1000 community plugins

Thanks to it's popularity, there's a large selection of available plugins for Jenkins. They can all be easily browsed over at https://plugins.jenkins.io/. The downside is that almost anything you want to do in Jenkins requires installing a plugin, even core functionality such as parsing output or checking out source code.
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 (Partial)

RSpec and Cucumber test suites can be integrated into Jenkins thanks to the large pool of available plugins and Ruby gems. Jenkins only understands the JUnit format natively.
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)

Yes (Partial)

Jest, AVA and other test suites can be integrated into Jenkins thanks to the large pool of available plugins and NPM packages. Jenkins only understands the JUnit format natively.
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

Allows integrations with other tools (ie: Slack, GitHub) or communication protocols (ie: email) via it's rich plugin suite
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

For use-cases that the +1k plugins don't cover, the Jenkins Remote API is yet another way to integrate Jenkins into your favorite tools or internal products.
Auditing

N/A

No

Jenkins instances are really managed by a sole user with administrative privileges. This can lead to various issues when it comes to audit trails / accountability.
Additional notes

How to run parallel tests on Travis CI and Jenkins
to execute 1-hour test suite in 2 minutes?

Without Knapsack Pro

you have to wait 20 minutes for slow tests running too long on the red node

Loading...

Run fast parallel CI build with Knapsack Pro

CI build completes work in only 10 minutes because Knapsack Pro ensures all parallel nodes finish work at a similar time

Loading...

You can even run 20 parallel nodes to complete your CI build in 2 minutes

How it works

Step 1

Install Knapsack Pro client in your project


Step 2

Update your CI server config file to run tests in parallel with Knapsack Pro


Step 3

Run a CI build with parallel tests using Knapsack Pro

Diagram that shows files distributed to 3 parallel CI nodes


Knapsack Pro in Queue Mode splits tests in a dynamic way across parallel CI nodes to ensure each CI node finishes work at a similar time. Thanks to that, your CI build time is as fast as possible. It works with many supported CI servers.

How to install it

Programming Language Supported test runners Installation guide Knapsack Pro Library
README / Source
Ruby RSpec, Cucumber, Minitest, test-unit, Spinach, Turnip Install knapsack_pro gem
JavaScript Cypress.io Install @knapsack-pro/cypress
JavaScript Jest Install @knapsack-pro/jest
JavaScript / TypeScript Any test runner in JavaScript How to build native integration with Knapsack Pro API to run tests in parallel for any test runner @knapsack-pro/core
Any programming language Any test runner How to build a custom Knapsack Pro API client from scratch in any programming language -

Do you use other programming language or test runner? Let us know.

Do you know

Start using Knapsack Pro

Sign up and speed up your tests.

Get faster feedback from Travis CI and Jenkins server

  • save time & money
  • deliver features faster
  • catch errors earlier
Knapsack Pro terminal

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

Continuous delivery pipelines in Jenkins and CI parallelisation

Travis CI parallelism integration

Jenkins parallelism integration

Introduction to CI parallelisation with Knapsack Pro

Run tests in parallel on Travis CI and Jenkins in the optimal way and avoid bottleneck parallel jobs.

How much can you save with faster tests
on Travis CI and Jenkins?

minutes
$

Monthly you can save hours
and up to $
on faster development cycle.

Features that make your tests perform better

Discover all features or see
how to use Knapsack Pro with your CI

Trusted solution

Join the teams optimizing their tests with Knapsack Pro.

We've been really enjoying Knapsack Pro, it's been saving us a ton of time.

Devin Brown Software Engineer at Pivotal

This is a fantastic product, it's been a total game-changer for us.

Geoff Harcourt CTO at CommonLit

We are using CircleCI and we noticed that builds were being limited by the slowest parallelized container. Knapsack Pro was really east to setup and we saw huge improvements right away. Thank you for making this tool!

Martin Sieniawski Software Engineer at Collage

Knapsack Pro has helped us build an insanely fast and scalable build pipeline with almost no setup or maintenance.

Tim Lucas Co-founder of buildkite.com

Knapsack Pro saves us hours of engineer waiting time every week, and is the best solution for keeping our tests load balanced that we've used to date.

Michael Amygdalidis Senior Software Engineer at Popular Pays

I've been playing with Queue Mode. Love it! Wow, I love how fast it goes.

Michael Menne CTO at humanagency.org

I just logged into my account expecting it to say that I needed to add a credit card and was so surprised and delighted to see the trial doesn't count usage by calendar days but by testing days! This is incredible! I love it!!!

I just wanted to say that I really appreciate that small but very huge feature. Thank you for being so thoughtful :)

Shannon Baffoni Senior Software Engineer
at Blue Bottle Coffee

See more testimonials

Start using Knapsack Pro with Travis CI or Jenkins

Sign up and speed up your tests.