Knapsack Pro
Knapsack Pro
TeamCityhttps://www.jetbrains.com/teamcity/ |
Netlify Buildhttps://www.netlify.com/products/build/ |
|
|---|---|---|
| Unique feature |
Technology awareness
|
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. |
| Type of product |
On Premise
|
SaaS
|
| Offers a free plan |
Yes They offer a great free professional plan, limited to 100 build configurations and 3 build agents. From there, you pay for each aditional agent you want (discounts if you purchase more than 1 agent at a time). They also provide a free plan for open source, non commercial projects, and steep 50% discounts for startups. |
Yes 300 build minutes/month, 1 concurrent CI build |
| Predictable pricing |
Yes They have a clear list of prices per number of agents. |
Yes Extra 500 build minutes costs $7/month. User seat $15/user/month. |
| Support / SLA |
Yes
|
Yes 99.99% uptime SLA for Starter and Pro plan. Business plan has negotiable SLA. |
|
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
|
Yes Starter plan (free) has only 1 concurrent build but Pro plan has 3 concurrent builds included. |
|
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 that we could find, but judging by the wording used it would appear that tasks can be divided accross different machines. |
Yes High-Performance Builds - The premium build environment gives more concurrency, processing power and asynchronous deploys. |
| Containers support / Build environment |
Yes First class Docker support, among others |
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. |
|
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 Great system overview, even allows building your own dashboards in order to see everything you're interested in at a glance. |
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. |
|
Management support
How easy is it to manage users / projects / assign roles and permissions and so on |
Yes Allows assigning roles, LDAP and Windows domain integrations and more. |
Yes Team members managment. Role-based access control only in business plan. |
| Self-hosted option |
Yes
|
No
|
| Hosted plans / SaaS |
No
|
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 Unlike most options in the CI/CD space, TeamCity allows defining pipelines using a Kotlin-based DSL. This unlocks a lot of potential, such as templates for common CI/CD tasks, and deep integration with various IDEs (not just JetBrains IDEs) |
Yes, partially Simple steps, define your own steps in bash commands |
|
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 Something that stands out from the rest, allows integrating third party reports, as long as they produce HTML output. |
No
|
|
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 JetBrains has a rich ecosystem of plugins in general. |
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. |
|
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 Using what they call 'Technology Awareness', promises great intehration with Ruby projects, with features such as testing framework support, static analysis and code coverage available out of the box, with no additional work required: https://www.jetbrains.com/teamcity/features/technology_awareness.html |
Yes It has support for Ruby. |
| Specific language support: JavaScript |
No (partial) Unlike Ruby, there's no first class support for Javascript, although they do advertise the fact that their large collections of plugins can cover any use case for Javascript projects: https://plugins.jetbrains.com/teamcity |
Yes It has support for JavaScript. |
|
Integrations
1st party support for common tools (like Slack notifications, various VCS platforms, etc) |
Yes Great cloud integrations (Google Cloud, AWS, VMWare, etc) as well as 'key' integrations (VSCode, Jira, even NuGet) |
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. |
|
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 Unlike most tools, which offer just a Rest API, TeamCity provides ample opportunity for extension via plugins, their own API, and service messages (formatted messages on stdout) |
No
|
| Auditing |
Yes
|
N/A
|
| Additional notes |
Great ecosystem, with a strong focus on integration with other tools (not only JetBrains). |
|