Knapsack Pro
Knapsack Pro
Github Actionshttps://github.com/features/actions |
Cirrus CIhttps://cirrus-ci.org |
|
|---|---|---|
| Unique feature |
Best GitHub integration possible
|
FreeBSD support
|
| Type of product |
SaaS / On Premise
|
SaaS / On Premise
|
| Offers a free plan |
Yes The 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. |
Yes Free for open source projects |
| 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) |
Yes Besides the seat (per-user access) you need to buy compute credits for running the build, priced differently depending on the machine you're running builds on. |
| Support / SLA |
Yes Community 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. |
N/A Not clear if they offer any real SLA on 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 Matrix builds allow concurrent jobs, even multi-platform. |
Yes There are limits on how many tasks can be run in parallel for the free tier builds: https://cirrus-ci.org/faq/#are-there-any-limits |
|
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 No specific mention, but given the fact that tasks can be run on multiple platforms, it's likely that distributed builds are also available. |
N/A
|
| Containers support / Build environment |
Yes Linux, macOS, Windows, and containers, or run directly in a VM. |
Yes Allows containers or VMs for every major operating system. |
|
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 Minimal 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/A Unclear from the available documentation |
N/A
|
| Self-hosted option |
Yes Coming soon, not available yet. |
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. |
Yes Called 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 Defined via YML config 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. |
N/A Unclear 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? |
Yes Thanks 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. |
Yes Unclear how, but they mention Ruby support specifically on the homepage |
No (partial) No specific support from what I can gather, but it does provide documentation for Ruby, including integration with the knapsack_pro gem. |
| Specific language support: JavaScript |
Yes Unclear how, but they mention Javascript (Node.js) support specifically on the homepage |
No No specific support and no documentation on setting up a CI/CD process for a Javascript project. |
|
Integrations
1st party support for common tools (like Slack notifications, various VCS platforms, etc) |
Yes Integrations made possible via the shared third party workflows available (AWS, Azure, Zeit, Kubernetes and many more) |
Yes Integrates well with GitHub - the whole CI/CD process starts with a commit to a GitHub repo. |
|
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/A Unclear at the moment, but assume GitHub Actions will be integrated with the GitHub GraphQL API (one of the more mature GraphQL API implementations available) |
Yes Provides a pretty nifty GraphQL API which allows querying the Cirrus CI Schema, as well as webhooks support for other types of custom integrations (such as Slack or IRC notifications, for example). They also added support for GitHub actions |
| Auditing |
N/A
|
N/A From what we can tell, there's no specific support for auditing changes in the Cirrus CI config (other than what is traceable via git commits to the YML config file) |
| Additional notes |
|
Seems to be used by companies with a solid engineering background (Google) |