Knapsack Pro
Knapsack Pro
Travis CIhttps://travis-ci.org |
Buildkitehttps://buildkite.com |
|
|---|---|---|
| Unique feature |
Build Matrix, ease of use, GitHub integration
|
Runs on own infrastructure, API
|
| Type of product |
SaaS, Self-hosted / On Premise
|
SaaS
|
| Offers a free plan |
Yes Free for open source projects |
Yes Free for open source projects and selected organizations |
| Predictable pricing |
Yes Clearly defined monthly plans, depending on concurrent jobs needed. |
Yes Clearly defined monthly and annual plans |
| Support / SLA |
Yes Available via email, or dedicated online interface for paid plans. |
Yes Depending on the plan, ranging from community support, all the way to an assigned Technical Manager, SLAs and live chat support. |
|
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 Run an unlimited number of concurrent agents, and an unlimited number of concurrent jobs. You can run your tests in isolated Docker container per agent. |
|
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 Run an unlimited number of concurrent agents, and an unlimited number of concurrent jobs |
| 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 Since the agents run on your own infra, you're free to do whatever |
|
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 The Buildkite UI features great vizualisations that feature build times, error rates, and more. |
|
Management support
How easy is it to manage users / projects / assign roles and permissions and so on |
N/A
|
Yes
|
| Self-hosted option |
Yes
|
No
|
| Hosted plans / SaaS |
Yes
|
Yes
|
|
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 Pipelines are defined using an Yaml config file and allow for great flexibility in defining what each step of the process does. |
|
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
|
|
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 Integrations for GitHub, GitLab, BitBucket as well as SSO support (Google Suite, SAML, GraphQL API). Growing number of community plugins: https://buildkite.com/plugins |
|
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 You can find useful plugins like https://github.com/sj26/rspec-buildkite https://github.com/ticky/simplecov-buildkite etc |
| 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
|
|
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 Integrations for GitHub, GitLab, BitBucket as well as SSO support (Google Suite, SAML, GraphQL API) |
|
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 Great GraphQL API, allows building your own dashboard with ease |
| Auditing |
N/A
|
Yes
|
| Additional notes |
|
|