Knapsack Pro
Knapsack Pro
Travis CIhttps://travis-ci.org |
Dronehttps://drone.io |
|
|---|---|---|
| Unique feature |
Build Matrix, ease of use, GitHub integration |
Customization |
| Type of product |
SaaS, Self-hosted / On Premise |
SaaS / On Premise |
| Offers a free plan |
YesFree for open source projects |
YesThe cloud version is free for open source projects. Also offers a free plan for any project, with a limit of 5000 builds per year. The on-premise version is available as a Docker image. |
| Predictable pricing |
YesClearly defined monthly plans, depending on concurrent jobs needed. |
YesPredictable pricing based on number of users and repositories. They have a calculator to help determine cost. |
| Support / SLA |
YesAvailable via email, or dedicated online interface for paid plans. |
N/AIt's not clear what their support commitment is. They have a fairly active community on Discourse, for community 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 |
YesTravisCI 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. |
YesPipeline task configuration allows running tasks in parallel |
|
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 |
YesPipelines can be configured to run on multiple machines, although they recommend that to be an option only if paralellizing tasks and scaling vertically doesn't suffice. They even support multi-platform distribution (ie: running tasks on various operating systems) |
| Containers support / Build environment |
YesTravisCI 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. |
YesBy default, they offer Docker support for the CI/CD job runners. |
|
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) |
YesAvailable by default in Travis (this is what most of the web UI consists of) |
Yes |
|
Management support
How easy is it to manage users / projects / assign roles and permissions and so on |
N/A |
YesThey offer in-depth documentation for user and server management. A lot of it can be done via the drone CLI tool, which seems to be the focal point of the docs. |
| Self-hosted option |
Yes |
Yes |
| 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. |
NoSpecifically built around GitHub pull requests. Pipelines can be defined, but parts of the process need to be implemented separatelly in GitHub. |
YesEasily configurable pipelines via YML files. |
|
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. |
N/A |
|
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 |
YesDrone CI allows integrating plugins into the CI/CD process. They have a list of available community plugins and provide documentation on building your own. Plugins are Docker containers which plug directly into the CI/CD process. |
|
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. |
YesTravisCI 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. |
No (partial)No specific support, but they do provide sufficient documentation on getting a Ruby project up and running, including a multi-platform example. |
| Specific language support: JavaScript |
YesTravisCI 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)No specific 1st party support, but the plugin marketplace features an NPM authoring and an NPM authentication plugin. |
|
Integrations
1st party support for common tools (like Slack notifications, various VCS platforms, etc) |
YesBy default, TravisCI is built to work with GitHub. Additionally, there is strong support for 3rd party tools like Coveralls, BrowserStack, etc. |
YesIntegrates well with source code management platforms (1st party support for GitHub, GitLab, BitBucket) as well as other systems via 3rd party plugins. |
|
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 |
YesOffers a feature-rich API that allows both reading data, as well as triggering or cancelling builds. |
YesDrone provides a feature-rich REST API, as well as an official Go SDK for it. |
| Auditing |
N/A |
Yes |
| Additional notes |
|
The fact that Drone works with any source code manager, as well as the fact that it can run tasks on multiple platforms makes it stand out from the rest. Very nifty! |