Netlify Buildhttps://www.netlify.com/products/build/ |
Scrutinizer CIhttps://scrutinizer-ci.com |
|
---|---|---|
Unique feature |
Deploy your sites to global Netlify infrastructure Every commit gets its own deployed version. Automatically attach a new Deploy Preview at a unique permanent URL whenever you submit a Pull/Merge Request. Set Netlify Build to deploy every branch in the repository for unlimited staging environments. |
Ongoing statical analysis
|
Type of product |
SaaS
|
SaaS
|
Offers a free plan |
Yes 300 build minutes/month, 1 concurrent CI build |
Yes Free for open source projects |
Predictable pricing |
Yes Extra 500 build minutes costs $7/month. User seat $15/user/month. |
Yes Three different paid monthly tiers |
Support / SLA |
Yes 99.99% uptime SLA for Starter and Pro plan. Business plan has negotiable SLA. |
N/A Not specifically mentioned, probably not. |
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 Starter plan (free) has only 1 concurrent build but Pro plan has 3 concurrent builds included. |
Yes Automated parallalelization for code analysis, as well as support for running tasks in parallel |
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 |
Yes High-Performance Builds - The premium build environment gives more concurrency, processing power and asynchronous deploys. |
N/A Unclear from the documentation (probably not) |
Containers support / Build environment |
Yes When you trigger a build on Netlify, their buildbot starts a Docker container to build your website. The buildbot will look for instructions about required languages and software needed to run your command before running build command. The instructions are called dependencies, and how you declare them depends on the programming languages and tools used in build. Build image selection is available. Until recently, all Netlify sites were built using the same build image. Netlify is experimenting with allowing customers to select from multiple Docker images with different operating systems and software versions. |
Yes Tests run in isolated containers. Docker support available. |
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 Simple dashboard to see CI builds. Other than CI analytics Netlify has Netlify Analytics that brings data captured directly from their servers for your website. |
Yes Besides classic CI overview, they also provide static code analysis insights, which is a differentiator for Scrutinizer |
Management support
How easy is it to manage users / projects / assign roles and permissions and so on |
Yes Team members managment. Role-based access control only in business plan. |
Yes Additional seats available for every plan at $14.90 per seat, per month. |
Self-hosted option |
No
|
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, partially Simple steps, define your own steps in bash commands |
Yes Pipelines as code (YML 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. |
No
|
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? |
No There are only small helpful things like incoming webhooks so other services can trigger Netlify deploys, and send outgoing webhooks as a deploy starts, succeeds, or fails. |
No
|
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 It has support for Ruby. |
Yes Code analysis (automated code reviews) are available for Ruby, as well as specific documentation for setting up a Ruby project: https://scrutinizer-ci.com/docs/guides/ruby. Frameworks like Ruby on Rails are supported. They also provide tools like bundler-audit, for identifying vulnerable gems: https://scrutinizer-ci.com/docs/tools/ruby/bundler-audit/ |
Specific language support: JavaScript |
Yes It has support for JavaScript. |
Yes Automated code reviews are available for Javascript as well as specific documentation for setting up a Node.js project: https://scrutinizer-ci.com/docs/guides/javascript. Typescript is also supported. |
Integrations
1st party support for common tools (like Slack notifications, various VCS platforms, etc) |
Yes Netlify has incoming webhooks so other services can trigger Netlify deploys, and send outgoing webhooks as a deploy starts, succeeds, or fails. For instance you can integrate it with Slack. |
Yes Light integration with third party systems, mainly code management frameworks like GitHub, Bitbucket, GitLab. |
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 |
No
|
Yes Comprehensive REST API available: https://scrutinizer-ci.com/docs/api/ |
Auditing |
N/A
|
N/A Unclear from the documentation, but most likely available. |
Additional notes |
|
The code analysis features seem great, the offer for similar tools is quite light. Seems similar to lgtm.com |