Knapsack Pro
Knapsack Pro
Github Actionshttps://github.com/features/actions |
CodeShiphttps://codeship.com |
|
|---|---|---|
| Unique feature |
Best GitHub integration possible |
Runs on own infrastructure |
| Type of product |
SaaS / On Premise |
SaaS |
| Offers a free plan |
YesThe on premise plan (not yet available) will be free, 2000 build minutes included in the free cloud plan. Completely free plan for open source projects. |
YesFree for up to 100 builds per month |
| Predictable pricing |
Yes (partial)While it's clear what the cost is (priced per build-minute), figuring out costs can be a hassle, especially as the price can vary quite a bit depending on commits to the project. One advantage for GitHub Actions is that the tiers define a maximum amount of minutes, so it's easier to predict the final cost. You can also purchase aditional runners with pricing dependent on the platform (MacOS, Linux, Windows) |
YesClearly defined, calculator, expensive |
| Support / SLA |
YesCommunity support available for any tier, unclear at what point and if dedicated support is available. Safe to assume that eneterprise clients can access technical support. |
YesOffers great dev 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 |
YesMatrix builds allow concurrent jobs, even multi-platform. |
YesVia easy Yaml config file, limited by the specs of the machine you have purchased |
|
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, but given the fact that tasks can be run on multiple platforms, it's likely that distributed builds are also available. |
No |
| Containers support / Build environment |
YesLinux, macOS, Windows, and containers, or run directly in a VM. |
YesNative support for Docker |
|
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) |
YesMinimal status overview definitely available, with live logs and GitHub integration. Unclear how far it goes. |
Yes |
|
Management support
How easy is it to manage users / projects / assign roles and permissions and so on |
N/AUnclear from the available documentation |
YesFull with organization and teams management |
| Self-hosted option |
YesComing soon, not available yet. |
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. |
YesCalled GitHub Action Workflows, they are defined in separate Docker containers, using the YAML syntax (they used to support HCL, but they're migrating away from that) |
Yes |
|
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. |
N/AUnclear from the available documentation |
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? |
YesThanks to the large following, GitHub Actions already enjoys a wide varierty of available pre-made workflows, which you can browse right on the homepage: https://github.com/features/actions |
N/A |
|
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. |
YesUnclear how, but they mention Ruby support specifically on the homepage |
YesFairly complete documentation on Ruby projects: https://documentation.codeship.com/pro/languages-frameworks/ruby/ |
| Specific language support: JavaScript |
YesUnclear how, but they mention Javascript (Node.js) support specifically on the homepage |
YesFairly complete documentation on Node.js projects: https://documentation.codeship.com/pro/languages-frameworks/nodejs/ |
|
Integrations
1st party support for common tools (like Slack notifications, various VCS platforms, etc) |
YesIntegrations made possible via the shared third party workflows available (AWS, Azure, Zeit, Kubernetes and many more) |
YesEasy to integrate a bunch of 3rd party services, such as Code Climate, Codecov, Rancher, Pager Duty and many more: https://documentation.codeship.com/general/integrations/codeclimate/ |
|
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 |
N/AUnclear at the moment, but assume GitHub Actions will be integrated with the GitHub GraphQL API (one of the more mature GraphQL API implementations available) |
YesCustom integrations are possible: https://documentation.codeship.com/general/integrations/custom-integration/ |
| Auditing |
N/A |
N/A |
| Additional notes |
|
CodeShip Pro gives you a lot more flexibility when defining your CI/CD process, plus you get your own AWS instance, so your build doesn't run on a shared server (this can be important for HIPAA or GDPR compliance, etc). |