Knapsack Pro
Knapsack Pro
Circle CIhttps://circleci.com |
Google Cloud Buildhttps://cloud.google.com/cloud-build/ |
|
|---|---|---|
| Unique feature |
Premium Support |
Security / speed |
| Type of product |
SaaS, Self-hosted / On Premise |
SaaS |
| Offers a free plan |
YesProvides a free plan for it's SaaS solution, for up to 1000 build minutes per month, 1 container and 1 concurrent job. On top of this, it has a special Free Tier for open source projects, which extend the number of containers and concurrent jobs available. |
YesGoogle offers a generous 120 build-minutes per day plan, not including time spent waiting in the queue. |
| Predictable pricing |
YesProvides a calculator, based on the number of concurrent jobs and containers, which can be used to determine pricing before purchase. They also give a guideline based on the number of developers you employ (2-3 containers per full-time developer) |
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 |
YesWhile it's community is not quite as vibrant as it is for Jenkins, CircleCI even offers support premium support for companies who cannot afford any downtime in their CI/CD pipelines (https://circleci.com/support/premium-support/). For the regular plans, all plans except the free tier offer official email support. The free tier only includes community support (Discuss, StackOverflow, etc.) |
YesEven available as a paid add-on, for 24/7 phone support for example: https://cloud.google.com/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 |
YesCircleCI can run builds in parallel, each build in a completely isolated environment by using containers. |
Yes |
|
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 |
YesThe SaaS version distributes builds by default, while the self-hosted version has all the tools built-in for managing the cluster of builder machines. |
N/A |
| Containers support / Build environment |
YesCircleCI runs every build in a container, or VM, ensuring an isolated, local scope for each build. The environment is also reset with each build, which can highlight hard-to-track issues related to assumptions about the environment that the project is deployed to. |
YesNative Docker and Packer support |
|
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) |
YesAvailable by default in Circle CI: https://circleci.com/docs/2.0/status/#section=jobs. Aditionally, the Insights Dashboard provides a very useful overview on build times, error rates and status for your projects: https://circleci.com/docs/2.0/insights/#section=jobs |
Yes |
|
Management support
How easy is it to manage users / projects / assign roles and permissions and so on |
No (partial)Using the Cloud plan for Circle CI requires no dedicated person for maintanence / management of the service. The CircleCI Server option (self-hosted) is also hassle free, as the process of installing and managing CircleCI and it's dependencies is automated. Developers are also given SSH acces to the builds (not the whole environment), while sys-admins can work on the host machine without worry about affecting the builds (which are containerized). |
Yes |
| Self-hosted option |
Yes |
No (partial)While there's no self hosted variant, they provide a local Cloud Build image which allows you to build locally, very valuable for debugging. |
| 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 in CircleCI are defined declaratively using an Yaml config file. CircleCI has special provisions for storing secrets in these files. |
YesConfigurable via YML and/or JSON 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. |
YesReports are available |
Yes |
|
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, partiallyWhile CircleCI doesn't natively support plugins, it's core features address all of the core functionality that a CI/CD service needs. For integrating with other platforms or tools, there are integrations such as https://slack.com/apps/A0F7VRE7N-circleci. Certain jobs are available as CircleCI Orbs: https://circleci.com/orbs/ |
YesThere are predefined images built for Cloud Build, which can be integrated right away in your build process. Some of them are first party: https://github.com/GoogleCloudPlatform/cloud-builders and others are community contributed: https://github.com/GoogleCloudPlatform/cloud-builders-community |
|
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. |
YesFor collecting test metadata and coverage, there is built-in support for Ruby (specifically, Cucumber and RSpec). Setting this up takes very little time and is well-documented on CircleCI's docs. |
N/ANothing specific as far as we can tell |
| Specific language support: JavaScript |
YesFor collecting test metadata and coverage, there is built-in support for Javascript. For code coverage, CircleCI understands Istanbul output (Jest also uses Istanbul for the code coverage reports), while for test metadata, the JUnit output format is natively supported. |
Yes (partial)npm, yarn and jasmine-node support via predefined Cloud Build steps. |
|
Integrations
1st party support for common tools (like Slack notifications, various VCS platforms, etc) |
YesAvailable as CircleCI Orbs: https://circleci.com/orbs/ |
YesVarious integrations available via custom Build Steps, as well as natively (Kubernetes, Docker, etc.) |
|
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 |
YesREST API documentation available at https://circleci.com/docs/api/#api-overview. Creating Orbs is also documented at https://circleci.com/docs/2.0/orb-author/#introduction |
YesREST API and comprehensive CLI tool, as well as a pub/sub system for build notifications. |
| Auditing |
N/A |
Yes |
| Additional notes |
|
Not unlike other Google tools, there's a strong emphasis on allowing developers to build on top of the service. Becomes more valuable if you're using other Google Cloud services as well. |