Concourse vs TeamCity

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

Concourse

259
390
+ 1
54
TeamCity

1.2K
1.1K
+ 1
316
Add tool

Concourse vs TeamCity: What are the differences?

## Key Differences Between Concourse and TeamCity

Concourse and TeamCity are both popular continuous integration and continuous delivery tools used in the software development process. However, there are key differences between the two platforms that can affect the choice of tool for a particular project. 

1. **Architecture**: Concourse follows a container-based architecture, where each job runs inside its own isolated container, ensuring that builds are reproducible and consistent. On the other hand, TeamCity uses build agents on traditional servers to execute build jobs, which can lead to potential conflicts or inconsistencies in build environments.

2. **Configuration Management**: Concourse relies on a pipeline declarative configuration format written in YAML, making it easier to define, version control, and maintain build pipelines. TeamCity, on the other hand, uses a web UI for configuring build jobs, which can be less transparent and harder to track changes over time.

3. **Dependency Handling**: Concourse has built-in support for managing job dependencies and ensuring that tasks run only when their dependencies are met. In contrast, TeamCity requires manual setup of build triggers and dependencies, which can be prone to errors and lead to unpredictable build outcomes.

4. **Scalability**: Concourse is designed with scalability in mind, as it can handle a large number of concurrent builds efficiently by distributing workload across multiple containers. TeamCity, while capable of scaling, may require additional configurations and resources to achieve the same level of scalability as Concourse.

5. **Community Support**: Concourse is an open-source project maintained by the community, which ensures a constant stream of updates, improvements, and plugins from the active user base. TeamCity, although feature-rich and robust, relies on JetBrains for updates and support, which may lead to a slower pace of development and lack of community-driven enhancements.

6. **Ecosystem Integration**: Concourse integrates seamlessly with cloud-native tools and technologies, making it an ideal choice for projects utilizing microservices, containers, and Kubernetes. TeamCity, while compatible with various software development tools, may require additional configuration and plugins to achieve the same level of integration with modern cloud technologies.

In Summary, Concourse and TeamCity differ in their architecture, configuration management, dependency handling, scalability, community support, and ecosystem integration, which can influence the choice of CI/CD tool for a particular project.
Advice on Concourse and TeamCity
Needs advice
on
ConcourseConcourse
and
JenkinsJenkins

I'm planning to setup complete CD-CD setup for spark and python application which we are going to deploy in aws lambda and EMR Cluster. Which tool would be best one to choose. Since my company is trying to adopt to concourse i would like to understand what are the lack of capabilities concourse have . Thanks in advance !

See more
Replies (1)
Maxi Krone
Cloud Engineer at fme AG · | 2 upvotes · 392.8K views
Recommends
on
ConcourseConcourse

I would definetly recommend Concourse to you, as it is one of the most advanced modern methods of making CI/CD while Jenkins is an old monolithic dinosaur. Concourse itself is cloudnative and containerbased which helps you to build simple, high-performance and scalable CI/CD pipelines. In my opinion, the only lack of skills you have with Concourse is your own knowledge of how to build pipelines and automate things. Technincally there is no lack, i would even say you can extend it way more easily. But as a Con it is more easy to interact with Jenkins if you are only used to UIs. Concourse needs someone which is capable of using CLIs.

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Concourse
Pros of TeamCity
  • 16
    Real pipelines
  • 10
    Containerised builds
  • 9
    Flexible engine
  • 6
    Fast
  • 4
    Open source
  • 3
    No Snowflakes
  • 3
    Simple configuration management
  • 2
    You have to do everything
  • 1
    Fancy Visualization
  • 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 Concourse
Cons of TeamCity
  • 2
    Fail forward instead of rollback pattern
  • 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 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.

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 Concourse and TeamCity as a desired skillset
What companies use Concourse?
What companies use TeamCity?
See which teams inside your own company are using Concourse 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 Concourse?
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 Concourse 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.
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.
Spinnaker
Created at Netflix, it has been battle-tested in production by hundreds of teams over millions of deployments. It combines a powerful and flexible pipeline management system with integrations to the major cloud providers.
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.
Ansible
Ansible is an IT automation tool. It can configure systems, deploy software, and orchestrate more advanced IT tasks such as continuous deployments or zero downtime rolling updates. Ansible’s goals are foremost those of simplicity and maximum ease of use.
See all alternatives