GoCD vs TeamCity

Need advice about which tool to choose?Ask the StackShare community!

GoCD

205
326
+ 1
206
TeamCity

1.1K
1.1K
+ 1
316
Add tool

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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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.

Advice on GoCD and TeamCity
Mohammad Hossein Amri
Chief Technology Officer at Planally · | 3 upvotes · 493.3K views
Needs advice
on
GoCDGoCD
and
JenkinsJenkins

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.

See more
Replies (1)
Ankit Malik
Software Developer at CloudCover · | 1 upvotes · 476.1K views
Recommends
on
Google Cloud BuildGoogle Cloud Build

Google cloud build can help you. It is hosted on cloud and also provide reasonable free quota.

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of GoCD
Pros of TeamCity
  • 31
    Open source
  • 27
    Pipeline dependencies
  • 25
    Pipeline structures
  • 22
    Can run jobs in parallel
  • 20
    Very flexible
  • 15
    Plugin architecture
  • 13
    Environments can keep config secure
  • 12
    Great UI
  • 10
    Good user roles and permissions
  • 9
    Supports many material dependencies
  • 7
    Fan-in, Fan-out
  • 6
    Designed for cd not just ci
  • 4
    Empowers product people to make delivery decisions
  • 2
    Flexible & easy deployment
  • 2
    Pass around artifacts
  • 1
    Build once
  • 61
    Easy to configure
  • 37
    Reliable and high-quality
  • 32
    User friendly
  • 32
    On premise
  • 32
    Github integration
  • 18
    Great UI
  • 16
    Smart
  • 12
    Free for open source
  • 12
    Can run jobs in parallel
  • 8
    Crossplatform
  • 5
    Chain dependencies
  • 5
    Fully-functional out of the box
  • 4
    Great support by jetbrains
  • 4
    REST API
  • 4
    Projects hierarchy
  • 4
    100+ plugins
  • 3
    Personal notifications
  • 3
    Free for small teams
  • 3
    Build templates
  • 3
    Per-project permissions
  • 2
    Upload build artifacts
  • 2
    Smart build failure analysis and tracking
  • 2
    Ide plugins
  • 2
    GitLab integration
  • 2
    Artifact dependencies
  • 2
    Official reliable support
  • 2
    Build progress messages promoting from running process
  • 1
    Repository-stored, full settings dsl with ide support
  • 1
    Built-in artifacts repository
  • 1
    Powerful build chains / pipelines
  • 1
    TeamCity Professional is FREE
  • 0
    High-Availability
  • 0
    Hosted internally

Sign up to add or upvote prosMake informed product decisions

Cons of GoCD
Cons of TeamCity
  • 2
    Lack of plugins
  • 2
    Horrible ui
  • 1
    No support
  • 3
    High costs for more than three build agents
  • 2
    Proprietary
  • 2
    User-friendly
  • 2
    User friendly

Sign up to add or upvote consMake informed product decisions

- No public GitHub repository available -

What is GoCD?

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.

What is TeamCity?

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.

Need advice about which tool to choose?Ask the StackShare community!

Jobs that mention GoCD and TeamCity as a desired skillset
What companies use GoCD?
What companies use TeamCity?
See which teams inside your own company are using GoCD or TeamCity.
Sign up for StackShare EnterpriseLearn More

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with GoCD?
What tools integrate with TeamCity?

Sign up to get full access to all the tool integrationsMake informed product decisions

Blog Posts

What are some alternatives to GoCD and TeamCity?
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.
GitLab CI
GitLab offers a continuous integration service. If you add a .gitlab-ci.yml file to the root directory of your repository, and configure your GitLab project to use a Runner, then each merge request or push triggers your CI pipeline.
Bamboo
Focus on coding and count on Bamboo as your CI and build server! Create multi-stage build plans, set up triggers to start builds upon commits, and assign agents to your critical builds and deployments.
Concourse
Concourse's principles reduce the risk of switching to and from Concourse, by encouraging practices that decouple your project from your CI's little details, and keeping all configuration in declarative files that can be checked into version control.
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.
See all alternatives