Knapsack Pro
Knapsack Pro
Shippablehttps://www.shippable.com |
Jenkinshttps://jenkins.io |
|
|---|---|---|
| Unique feature |
N/A |
Plugins |
| Type of product |
SaaS / On Premise |
Self-hosted / On Premise |
| Offers a free plan |
YesFree 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. |
YesFree, open source software |
| Predictable pricing |
YesClear 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) |
YesJenkins is free software, the only costs are those assigned to running your infrastructure. |
| Support / SLA |
YesOne 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 |
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 |
YesOne 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 |
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/ANo 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. |
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 |
YesNative Docker support |
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) |
YesDetailed 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. |
YesAvailable 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 |
Yes |
NoIn 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 |
YesJenkins is Open Source Software, and self-hosting is the only way to use it. |
| Hosted plans / SaaS |
Yes |
NoOnly 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. |
YesConfigurable via an YML file (called Assembly Lines) |
YesOffers 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 |
YesHas 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? |
Yeshttps://www.shippable.com/integrations.html |
> 1000 community pluginsThanks 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. |
YesRuby 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/ |
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 |
YesSpecific documentation for Node.js available: http://docs.shippable.com/ci/ruby-continuous-integration/ |
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) |
Yeshttp://docs.shippable.com/ci/ruby-continuous-integration/ |
YesAllows 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 |
YesProvides 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/ |
YesFor 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 |
Yes |
NoJenkins 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 |
|
|