Knapsack Pro
Knapsack Pro
Travis CIhttps://travis-ci.org |
Shippablehttps://www.shippable.com |
|
|---|---|---|
| Unique feature |
Build Matrix, ease of use, GitHub integration
|
N/A
|
| Type of product |
SaaS, Self-hosted / On Premise
|
SaaS / On Premise
|
| Offers a free plan |
Yes Free for open source projects |
Yes Free unlimited builds for open source projects, 150 builds per month for all others (hosted plan). For the on-premise solution they only offer a 30 day trial. |
| Predictable pricing |
Yes Clearly defined monthly plans, depending on concurrent jobs needed. |
Yes Clear pricing based on number of concurrent jobs. They also allow a varied combination of platforms you want to run (Ubuntu, Windows, MacOS, CentOS) and provide a Bring Your Own Node option (so you can run builds on your own infrastructure) |
| Support / SLA |
Yes Available via email, or dedicated online interface for paid plans. |
Yes One of the few competitors to offer support tiers with clearly defined SLAs: https://www.shippable.com/premium-support.html as well as Services and Training: https://www.shippable.com/devops-services.html |
|
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 One thing that stands out, is the shipctl CLI tool, which can automatically determine which tests to run in parallel, based on previous performance, such that a minimal amount of time is ensured: http://docs.shippable.com/ci/running-parallel-tests/#running-tests-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
|
N/A No specific mention. From the wording, multiple environments are certainly available, but it's unclear if the tasks can be distributed to multiple containers/VMs on the same machine, or multiple 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 Native Docker support |
|
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 Detailed statistics available at multiple levels (job, account, project, etc.). They also include a view they call SPOG (Single Pane of Glass) which allows viewing a real-time representation of all of the pipelines in the organization, from where you can drill-in to the leaf nodes you're interested in. |
|
Management support
How easy is it to manage users / projects / assign roles and permissions and so on |
N/A
|
Yes
|
| 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. |
No Specifically built around GitHub pull requests. Pipelines can be defined, but parts of the process need to be implemented separatelly in GitHub. |
Yes Configurable via an YML file (called Assembly Lines) |
|
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 https://www.shippable.com/integrations.html |
|
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 Ruby is available by default on the Shippable container images. They also provide support for tools such as Cucumber or RSpec. Specific documentation for Ruby available on the website: http://docs.shippable.com/ci/ruby-continuous-integration/ |
| 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 Specific documentation for Node.js available: http://docs.shippable.com/ci/ruby-continuous-integration/ |
|
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 http://docs.shippable.com/ci/ruby-continuous-integration/ |
|
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 Provides a straight-forward REST API: http://docs.shippable.com/platform/api/api-overview/. They also provide ways to integrate notifications in your workflow, via webhooks or specific channels (IRC, Slack, Email, etc): http://docs.shippable.com/ci/send-notifications/ |
| Auditing |
N/A
|
Yes
|
| Additional notes |
|
|