Knapsack Pro
Knapsack Pro
AppVeyorhttps://www.appveyor.com |
TeamCityhttps://www.jetbrains.com/teamcity/ |
|
|---|---|---|
| Unique feature |
Supports NuGet packages / Windows build environment
|
Technology awareness
|
| Type of product |
SaaS / On Premise
|
On Premise
|
| Offers a free plan |
Yes Free SaaS plan for open source projects. There is also a free on premise version, but it's quite limited (1 user, 1 team, community support) |
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. |
| Predictable pricing |
Yes Very simple pricing plans: 3 options for the SaaS version, two options for the on premise option. No variable pricing. |
Yes They have a clear list of prices per number of agents. |
| Support / SLA |
Yes All paid on premise plans offer support, as well as the two higher priced SaaS plans. Only community support available for the free on premise version and the lowest SaaS tier. |
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 Allows splitting tests to run on different VMs in parallel. |
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 |
N/A
|
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. |
| Containers support / Build environment |
Yes Runs every build in a VM, and it offers several options depending on the plan (SaaS or self-hosted) as well sa personal preference. |
Yes First class Docker support, among others |
|
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 The dashboard is not as great as for other options in the market, but allows seeing project status at a glance. |
Yes Great system overview, even allows building your own dashboards in order to see everything you're interested in at a glance. |
|
Management support
How easy is it to manage users / projects / assign roles and permissions and so on |
Yes Allows creating teams and assigning roles. There is some integration with GitHub Teams but the concepts are different which might be tricky depending on how the GitHub project is managed, for instance. |
Yes Allows assigning roles, LDAP and Windows domain integrations and more. |
| Self-hosted option |
Yes
|
Yes
|
| Hosted plans / SaaS |
Yes
|
No
|
|
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 There is a single predefined possible pipeline, which defines various hooks (such as before_build / after_build). The pipeline can be configured via the UI or via an appveyor.yml file. The two are mutually exclusive, so it's either one or the other. |
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) |
|
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 Notifications are highly configurable, but visual reports such as code coverage is not easy to implement. |
Yes Something that stands out from the rest, allows integrating third party reports, as long as they produce HTML output. |
|
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
|
Yes JetBrains has a rich ecosystem of plugins in general. |
|
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 Many Ruby gems use AppVeyor as their CI server of choice. Among the features for Ruby are the pre-installed Ruby versions on both Windows and Ubuntu servers, as well as the appveyor-worker gem which makes it easy to report status during the build process. |
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 |
| Specific language support: JavaScript |
Yes Comes with node.js and io.js versions pre-installed. Also offers documentation on npm integration on their website. |
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 |
|
Integrations
1st party support for common tools (like Slack notifications, various VCS platforms, etc) |
Yes Probably the most notable aspect here is the large array of deployment integrations available (from simple FTP uploads to Azure servers or NuGet packages). |
Yes Great cloud integrations (Google Cloud, AWS, VMWare, etc) as well as 'key' integrations (VSCode, Jira, even NuGet) |
|
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 Offers a basic CRUD REST API for querying projects and builds as well as a real-time Build Worker API which can send updates on build status. |
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) |
| Auditing |
N/A
|
Yes
|
| Additional notes |
Very Windows oriented |
Great ecosystem, with a strong focus on integration with other tools (not only JetBrains). |