GoCD vs TeamCity

Overview

TeamCity

Stacks1.2K

Followers1.1K

Votes316

GoCD

Stacks205

Followers325

Votes207

GitHub Stars7.3K

Forks980

GoCD vs TeamCity: What are the differences?

Introduction In this markdown, we will highlight the key differences between GoCD and TeamCity for easy website integration.

Deployment Management: GoCD focuses on continuous delivery and provides extensive deployment management capabilities out of the box, allowing users to easily visualize and control the deployment pipelines. On the other hand, TeamCity primarily focuses on continuous integration and lacks some of the deployment management features present in GoCD.
Plugin Ecosystem: TeamCity has a vast plugin ecosystem with a wide range of plugins available for various integrations and customization options, providing users with flexibility and extensibility. In contrast, GoCD has a smaller plugin ecosystem compared to TeamCity, limiting the customization and integration options available to users.
Configuration as Code: GoCD supports configuration as code, allowing users to define pipeline configurations using code-based configuration files, enabling better tracking of changes and version control. TeamCity, though capable of defining configurations through the UI, lacks native support for configuration as code, potentially making it harder to manage configurations for larger projects.
Open Source vs. Commercial: GoCD is an open-source tool with a strong community support and active development, making it a cost-effective option for many organizations. In contrast, TeamCity is a commercial product with additional features and support provided by JetBrains, which may be preferred by larger enterprises requiring enterprise-level support and features.
Scalability and Performance: GoCD is designed to scale well for large and complex pipelines, offering better performance and scalability features compared to TeamCity. While TeamCity is suitable for smaller to medium-sized projects, GoCD may be a better choice for organizations with larger and more complex pipeline requirements.
Ease of Use: TeamCity is known for its user-friendly interface and ease of use, making it easier for beginners to get started with building and running pipelines. GoCD, while powerful, may have a steeper learning curve due to its more complex configuration and deployment management features.

In Summary, the key differences between GoCD and TeamCity lie in their focus on deployment management, plugin ecosystem, configuration as code support, pricing model, scalability, and ease of use.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on TeamCity, GoCD

Mohammad Hossein

Chief Technology Officer at Planally

Apr 17, 2020

Needs adviceon

Docker

I'm open to anything. just want something that break less and doesn't need me to pay for it, and can be hosted on Docker. our scripting language is powershell core. so it's better to support it. also we are building dotnet core in our pipeline, so if they have anything related that helps with the CI would be nice.

545k views545k

Comments

Detailed Comparison

TeamCity	GoCD
TeamCity is a user-friendly continuous integration (CI) server for professional developers, build engineers, and DevOps. It is trivial to setup and absolutely free for small teams and open source projects.	GoCD is an open source continuous delivery server created by ThoughtWorks. GoCD offers business a first-class build and deployment engine for complete control and visibility.
Automate code analyzing, compiling, and testing processes, with having instant feedback on build progress, problems, and test failures, all in a simple, intuitive web-interface; Simplified setup: create projects from just a VCS repository URL;Run multiple builds and tests under different configurations and platforms simultaneously; Make sure your team sustains an uninterrupted workflow with the help of Pretested commits and Personal builds; Have build history insight with customizable statistics on build duration, success rate, code quality, and custom metrics; Enable cost-effective on-demand build infrastructure scaling thanks to tight integration with Amazon EC2; Easily extend TeamCity functionality and add new integrations using Java API; Great visual project representation. Track any changes made by any user in the system, filter projects and choose style of visual change status representation;	Model complex workflows with dependency management and parallel execution; Easy to pass once-built binaries between stages; Visibility into your end-to-end workflow. Track a change from commit to deploy at a glance; Manual triggers allow deployment any version at anytime. And it's securable and auditable; Run tests written in most languages or frameworks, provides informative testing report; Compare both files and commit messages across any two arbitrary builds; Eliminate Bottlenecks by providing trivial parallel execution across pipelines, platforms, versions, branches, etc.; Easily reuse pipeline configurations via template system.
Statistics
GitHub Stars -	GitHub Stars 7.3K
GitHub Forks -	GitHub Forks 980
Stacks 1.2K	Stacks 205
Followers 1.1K	Followers 325
Votes 316	Votes 207
Pros & Cons
Pros 61 Easy to configure 37 Reliable and high-quality 32 On premise 32 Github integration 32 User friendly Cons 3 High costs for more than three build agents 2 User friendly 2 Proprietary 2 User-friendly	Pros 32 Open source 27 Pipeline dependencies 25 Pipeline structures 22 Can run jobs in parallel 20 Very flexible Cons 2 Lack of plugins 2 Horrible ui 1 No support
Integrations
Slack	Docker Kubernetes Slack

What are some alternatives to TeamCity, GoCD?

Jenkins

In a nutshell Jenkins CI is the leading open-source continuous integration server. Built with Java, it provides over 300 plugins to support building and testing virtually any project.

Travis CI

Free for open source projects, our CI environment provides multiple runtimes (e.g. Node.js or PHP versions), data stores and so on. Because of this, hosting your project on travis-ci.com means you can effortlessly test your library or applications against multiple runtimes and data stores without even having all of them installed locally.

Codeship

Codeship runs your automated tests and configured deployment when you push to your repository. It takes care of managing and scaling the infrastructure so that you are able to test and release more frequently and get faster feedback for building the product your users need.

CircleCI

Continuous integration and delivery platform helps software teams rapidly release code with confidence by automating the build, test, and deploy process. Offers a modern software development platform that lets teams ramp.

Drone.io

Drone is a hosted continuous integration service. It enables you to conveniently set up projects to automatically build, test, and deploy as you make changes to your code. Drone integrates seamlessly with Github, Bitbucket and Google Code as well as third party services such as Heroku, Dotcloud, Google AppEngine and more.

wercker

Wercker is a CI/CD developer automation platform designed for Microservices & Container Architecture.

Shippable

Shippable is a SaaS platform that lets you easily add Continuous Integration/Deployment to your Github and BitBucket repositories. It is lightweight, super simple to setup, and runs your builds and tests faster than any other service.

Buildkite

CI and build automation tool that combines the power of your own build infrastructure with the convenience of a managed, centralized web UI. Used by Shopify, Basecamp, Digital Ocean, Venmo, Cochlear, Bugsnag and more.

Snap CI

Snap CI is a cloud-based continuous integration & continuous deployment tool with powerful deployment pipelines. Integrates seamlessly with GitHub and provides fast feedback so you can deploy with ease.

Appveyor

AppVeyor aims to give powerful Continuous Integration and Deployment tools to every .NET developer without the hassle of setting up and maintaining their own build server.

Related Comparisons

Bitbucket vs GitHub vs GitLab

AWS CodeCommit vs Bitbucket vs GitHub

Docker Swarm vs Kubernetes vs Rancher

Grunt vs Webpack vs gulp

Grafana vs Graphite vs Kibana

GoCD vs TeamCity: What are the differences?

Introduction In this markdown, we will highlight the key differences between GoCD and TeamCity for easy website integration.

Deployment Management: GoCD focuses on continuous delivery and provides extensive deployment management capabilities out of the box, allowing users to easily visualize and control the deployment pipelines. On the other hand, TeamCity primarily focuses on continuous integration and lacks some of the deployment management features present in GoCD.
Plugin Ecosystem: TeamCity has a vast plugin ecosystem with a wide range of plugins available for various integrations and customization options, providing users with flexibility and extensibility. In contrast, GoCD has a smaller plugin ecosystem compared to TeamCity, limiting the customization and integration options available to users.
Configuration as Code: GoCD supports configuration as code, allowing users to define pipeline configurations using code-based configuration files, enabling better tracking of changes and version control. TeamCity, though capable of defining configurations through the UI, lacks native support for configuration as code, potentially making it harder to manage configurations for larger projects.
Open Source vs. Commercial: GoCD is an open-source tool with a strong community support and active development, making it a cost-effective option for many organizations. In contrast, TeamCity is a commercial product with additional features and support provided by JetBrains, which may be preferred by larger enterprises requiring enterprise-level support and features.
Scalability and Performance: GoCD is designed to scale well for large and complex pipelines, offering better performance and scalability features compared to TeamCity. While TeamCity is suitable for smaller to medium-sized projects, GoCD may be a better choice for organizations with larger and more complex pipeline requirements.
Ease of Use: TeamCity is known for its user-friendly interface and ease of use, making it easier for beginners to get started with building and running pipelines. GoCD, while powerful, may have a steeper learning curve due to its more complex configuration and deployment management features.

In Summary, the key differences between GoCD and TeamCity lie in their focus on deployment management, plugin ecosystem, configuration as code support, pricing model, scalability, and ease of use.