Need advice about which tool to choose?Ask the StackShare community!
GoCD vs TeamCity: What are the differences?
Developers describe GoCD as "Open source continuous delivery tool allows for advanced workflow modeling and dependencies management". 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. On the other hand, TeamCity is detailed as "TeamCity is an ultimate Continuous Integration tool for professionals". 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 and TeamCity can be categorized as "Continuous Integration" tools.
Some of the features offered by GoCD are:
- 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
On the other hand, TeamCity provides the following key features:
- 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
"Open source" is the top reason why over 29 developers like GoCD, while over 52 developers mention "Easy to configure" as the leading cause for choosing TeamCity.
GoCD is an open source tool with 5.07K GitHub stars and 796 GitHub forks. Here's a link to GoCD's open source repository on GitHub.
Stack Exchange, ebay, and Apple are some of the popular companies that use TeamCity, whereas GoCD is used by Auto Trader, Hazeorid, and OpenX. TeamCity has a broader approval, being mentioned in 237 company stacks & 351 developers stacks; compared to GoCD, which is listed in 40 company stacks and 78 developer stacks.
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.

Google cloud build can help you. It is hosted on cloud and also provide reasonable free quota.
Pros of GoCD
- Open source32
- Pipeline dependencies27
- Pipeline structures25
- Can run jobs in parallel22
- Very flexible20
- Plugin architecture15
- Environments can keep config secure13
- Great UI12
- Good user roles and permissions10
- Supports many material dependencies9
- Fan-in, Fan-out7
- Designed for cd not just ci6
- Empowers product people to make delivery decisions4
- Flexible & easy deployment2
- Pass around artifacts2
- Build once1
Pros of TeamCity
- Easy to configure60
- Reliable and high-quality37
- User friendly31
- Github integration31
- On premise31
- Great UI18
- Smart16
- Can run jobs in parallel12
- Free for open source12
- Crossplatform8
- Great support by jetbrains4
- Chain dependencies4
- REST API4
- Fully-functional out of the box4
- Projects hierarchy4
- Build templates3
- Per-project permissions3
- Personal notifications3
- Free for small teams3
- 100+ plugins3
- Ide plugins2
- GitLab integration2
- Build progress messages promoting from running process2
- Artifact dependencies2
- Smart build failure analysis and tracking2
- Upload build artifacts2
- Built-in artifacts repository1
- Powerful build chains / pipelines1
- TeamCity Professional is FREE1
- Repository-stored, full settings dsl with ide support1
- Hosted internally0
- Official reliable support0
- High-Availability0
Sign up to add or upvote prosMake informed product decisions
Cons of GoCD
- Lack of plugins2
- Horrible ui2
- No support1
Cons of TeamCity
- User friendly2
- Proprietary1
- High costs for more than three build agents1
- User-friendly1