Knapsack Pro
Knapsack Pro
CodeFresh CIhttps://codefresh.io |
Cirrus CIhttps://cirrus-ci.org |
|
|---|---|---|
| Unique feature |
Built for Kubernetes |
FreeBSD support |
| Type of product |
SaaS / On Premise |
SaaS / On Premise |
| Offers a free plan |
YesOffers a minimal free plan (only one concurrent job, 3 users, various other limitations) |
YesFree for open source projects |
| Predictable pricing |
YesEasy price calculator, based on the number of machines, concurrent jobs and special features. |
YesBesides 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 |
YesPaid support for enterprise plans |
N/ANot 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 |
YesThere 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/AUnclear from the documentation (probably not) |
N/A |
| Containers support / Build environment |
YesBuilt for Kubernetes, so containers are a must. |
YesAllows 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) |
YesThey seem to provide pretty great status overview, depending on the type of plan you're using. |
Yes |
|
Management support
How easy is it to manage users / projects / assign roles and permissions and so on |
Yes |
N/A |
| Self-hosted option |
YesOnly available for enterprise plans |
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. |
YesPipelines as code (YML files) |
YesDefined 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. |
Yes |
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? |
YesEvery step in a CodeFresh pipeline is a Docker image. A wide array of steps is available over at https://steps.codefresh.io/ |
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. |
YesSpecific documentation for a sample Ruby-on-Rails project: https://codefresh.io/docs/docs/learn-by-example/ruby/ |
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 |
YesThere's an 'npm publish' step available, and they also provide a few Javascript examples over at https://codefresh.io/docs/docs/learn-by-example/nodejs/ (one is just a sample, one is a little more complex, using Redis, Python, etc., and one is a React App) |
NoNo 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) |
Yeshttps://steps.codefresh.io |
YesIntegrates 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 |
YesRich REST API available, well documented at https://g.codefresh.io/api/ |
YesProvides 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 |
YesAudit logs available: https://codefresh.io/docs/docs/enterprise/audit-logs/ |
N/AFrom 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) |