Knapsack Pro
Knapsack Pro
TeamCityhttps://www.jetbrains.com/teamcity/ |
Gitlab CIhttps://about.gitlab.com/product/continuous-integration/ |
|
|---|---|---|
| Unique feature |
Technology awareness
|
AutoDev Ops / Allows keeping code management and CI in the same place
|
| Type of product |
On Premise
|
SaaS / On Premise
|
| 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 Very generous free plans for both the SaaS version as well as the on premise version. |
| Predictable pricing |
Yes They have a clear list of prices per number of agents. |
Yes Clear and affordable pricing for both SaaS and self-hosted versions. |
| Support / SLA |
Yes
|
Yes All paid plans include next business day 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 |
Yes
|
Yes Easily configure jobs you want to be run in parallel via the YML config file (gitlab-ci.yml) |
|
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
|
| Containers support / Build environment |
Yes First class Docker support, among others |
Yes The Docker Container Registry is integrated into GitLab by default |
|
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
|
|
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
|
| Self-hosted option |
Yes
|
Yes
|
| 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 Defined via YML config 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. |
Yes Something that stands out from the rest, allows integrating third party reports, as long as they produce HTML output. |
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 JetBrains has a rich ecosystem of plugins in general. |
Yes
|
|
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 Although not built into GitLab CI by default, the Docker support allows solving any Ruby specific need that may arise. |
| 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 Although not built into GitLab CI by default, the Docker support allows solving any Javascript specific need that may arise. |
|
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 Plenty of third party integrations available throughout GitLab, most notably Kubernetes and GitHub, but also plenty of others: https://docs.gitlab.com/ee/integration/README.html |
|
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) |
Yes Provides a REST API and a (new) GraphQL API, with plans to maintain the GraphQL API only going forward. Allows doing almost anything that can be done via the interface, at least in terms of CI needs. |
| Auditing |
Yes
|
Yes
|
| Additional notes |
Great ecosystem, with a strong focus on integration with other tools (not only JetBrains). |
The Auto DevOps feature might be interesting to people looking for a very hands-off experience with getting a CI/CD process up and running https://docs.gitlab.com/ee/topics/autodevops/ |