Knapsack Pro
Knapsack Pro
Cirrus CIhttps://cirrus-ci.org |
AWS CodeBuildhttps://aws.amazon.com/codebuild/ |
|
|---|---|---|
| Unique feature |
FreeBSD support
|
AWS integration
|
| Type of product |
SaaS / On Premise
|
SaaS
|
| Offers a free plan |
Yes Free for open source projects |
Yes The AWS free-tier includes 100 build-minutes per month, on their smallest machine. It's unclear, but it seems like this applies only to the first year of service. |
| Predictable pricing |
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. |
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. |
| Support / SLA |
N/A Not clear if they offer any real SLA on support. |
Yes
|
|
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 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 |
N/A
|
|
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
|
| Containers support / Build environment |
Yes Allows containers or VMs for every major operating system. |
Yes Builds run in specific-to-the-project, isolated environments |
|
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
|
Yes Offers minimal information built in, but allows integrations with tools such as CloudWatch (another Amazon product), or streaming build information to your own API, for more in-depth analysis. |
|
Management support
How easy is it to manage users / projects / assign roles and permissions and so on |
N/A
|
Yes Professional user management via AWS Identity and Access Management: https://aws.amazon.com/iam/ |
| Self-hosted option |
Yes
|
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. |
Yes Defined via YML config files |
Yes As it's usually the case with Amazon, CodeBuild simply provides the 'build' part of a true CI/CD system, while pipelines are managed via CodePipeline, another Amazon product: https://aws.amazon.com/codepipeline/pricing/?nc=sn&loc=3 |
|
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
|
Yes Offers minimal information built in, but allows integrations with tools such as CloudWatch (another Amazon product), or streaming build information to your own API, for more in-depth analysis. |
|
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? |
N/A
|
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. |
No (partial) No specific support from what I can gather, but it does provide documentation for Ruby, including integration with the knapsack_pro gem. |
No (partial) The environments available on CodeBuilt include Ruby pre-installed: https://docs.aws.amazon.com/codebuild/latest/userguide/build-env-ref-available.html, but that seems to be as far as specific support goes |
| Specific language support: JavaScript |
No No specific support and no documentation on setting up a CI/CD process for a Javascript project. |
No (partial) The environments available on CodeBuilt include Node pre-installed: https://docs.aws.amazon.com/codebuild/latest/userguide/build-env-ref-available.html, but that seems to be as far as specific support goes |
|
Integrations
1st party support for common tools (like Slack notifications, various VCS platforms, etc) |
Yes Integrates well with GitHub - the whole CI/CD process starts with a commit to a GitHub repo. |
Yes CodeBuild builds can be connected to sources such as GitHub or BitBucket, but being an Amazon Service, the deepest integrations are with other Amazon Code services (CodePipeline, CodeDeploy, and others: https://aws.amazon.com/products/developer-tools/) |
|
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 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 |
Yes Amazon SDKs can be used to interact with CodeBuild |
| Auditing |
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) |
Yes
|
| Additional notes |
Seems to be used by companies with a solid engineering background (Google) |
Like most things Amazon, it becomes more valuable as you acquire and integrate various Amazon solutions, not necesarily as a standalone tool. |