Concourse for VMware Tanzu vs TeamCity comparison

Cancel
You must select at least 2 products to compare!
Comparison Buyer's Guide
Executive Summary

We performed a comparison between Concourse for VMware Tanzu and TeamCity based on real PeerSpot user reviews.

Find out what your peers are saying about GitLab, Jenkins, Google and others in Build Automation.
To learn more, read our detailed Build Automation Report (Updated: March 2024).
765,386 professionals have used our research since 2012.
Featured Review
Quotes From Members
We asked business professionals to review the solutions they use.
Here are some excerpts of what they said:
Pros
"We never experienced any problems with scalability."

More Concourse for VMware Tanzu Pros →

"TeamCity's GUI is nice.""We would like to see better integration with other version controls, since we encountered difficulty when this we first attempted.""The most valuable aspect of the solution is its easy configuration. It also has multiple plugins that can be used especially for building .net applications.""TeamCity is a very user-friendly tool.""Using TeamCity and emailing everyone on fail is one way to emphasize the importance of testing code and showing management why taking the time to test actually does saves time from having to fix bugs on the other end.""It's easy to move to a new release because of templates and meta-runners, and agent pooling.""Good integration with IDE and JetBrains products.""TeamCity is very useful due to the fact that it has a strong plug-in system."

More TeamCity Pros →

Cons
"I would like to see additional support for things outside of Cloud Foundry."

More Concourse for VMware Tanzu Cons →

"If there was more documentation that was easier to locate, it would be helpful for users.""The UI for this solution could be improved. New users don't find it easy to navigate. The need some level of training to understand the ins and the outs.""Last time I used it, dotnet compilation had to be done via PowerShell scripts. There was actually a lot that had to be scripted.""It will benefit this solution if they keep up to date with other CI/CD systems out there.""I need some more graphical design.""The upgrade process could be smoother. Upgrading major versions can often cause some pain.""Their online documentation is fairly extensive, but sometimes you can end up navigating in circles to find answers. I would like them (or partner with someone)​ to provide training classes to help newcomers get things up and running more quickly.""We've called TeamCity tech support. Unfortunately, all their tech support is based in Europe, so we end up with such a big time crunch that I now need to have one person in the US."

More TeamCity Cons →

Pricing and Cost Advice
  • "The solution is bundled in with Cloud Foundry so the pricing is not independent."
  • More Concourse for VMware Tanzu Pricing and Cost Advice →

  • "Start with the free tier for a few build configs and see how it works for you, then according to your scale find the enterprise license which fits you the most."
  • "The licensing is on an annual basis."
  • More TeamCity Pricing and Cost Advice →

    report
    Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
    765,386 professionals have used our research since 2012.
    Comparison Review
    Anonymous User
    Moving to TeamCity from Jenkins At work, we’re slowly migrating from Jenkins to TeamCity in the hope of ending some of our recurring problems with continuous integration. My use of Jenkins prior to this job has been almost strictly on a personal basis, although I pretty much only use Travis nowadays. The biggest difference upon initial inspection is that TeamCity is far more focused on validating individual commits rather than certain types of tests. Jenkins’ front page presents information that is simply not useful in a non-linear development environment, where people are often working in vastly different directions. How many of the previous tests passed/failed is not really salient information in this kind of situation. Running specific tests for individual commits on TeamCity is far more trivial in terms of interface complexity than Jenkins. TeamCity just involves clicking the ”…” button in the corner on any test type (although I wish it wasn’t so easy to click “Run” by accident). I generally find TeamCity a lot more intuitive than Jenkins out of the box. There’s a point at which you feel that if you have to scour the documentation to do anything remotely complex in an application, you’re dealing with a bad interface. One disappointing thing in both is that inter-branch merges improperly trigger e-mails to unrelated committers. I suppose it is fairly difficult to determine who to notify about failure in situations like these, though. It seems like TeamCity pulls up the… Read more →
    Questions from the Community
    Top Answer:We never experienced any problems with scalability.
    Top Answer:The solution is bundled in with Cloud Foundry so the pricing is not independent.
    Top Answer:The biggest gap for me was just that the solution is relatively tied to Cloud Foundry. If you have anything you need to deploy outside of that, it becomes burdensome. I would like to see additional… more »
    Top Answer:TeamCity is a very user-friendly tool.
    Top Answer:It's open source, however, if you want your solution to be deployed on their cloud or on the cloud in general without you being involved and having it and managed by them, there may be costs involved… more »
    Top Answer:It's just a tool that I used. I needed to deliver something, so I did. I wasn't looking at it in a way to criticize it or to optimize it. As a user, I need some more graphical design. For example, in… more »
    Ranking
    15th
    out of 41 in Build Automation
    Views
    660
    Comparisons
    622
    Reviews
    1
    Average Words per Review
    246
    Rating
    7.0
    6th
    out of 41 in Build Automation
    Views
    3,476
    Comparisons
    3,016
    Reviews
    2
    Average Words per Review
    574
    Rating
    8.0
    Comparisons
    Also Known As
    Pivotal Concourse, Concourse for PCF, Concourse
    Learn More
    Overview

    Continuous integration for application developers:

    Concourse for VMware Tanzu is a CI/CD system remastered for teams that practice agile development and deliver frequently to one or many cloud platforms.

    TeamCity is a Continuous Integration and Deployment server that provides out-of-the-box continuous unit testing, code quality analysis, and early reporting on build problems. A simple installation process lets you deploy TeamCity and start improving your release management practices in a matter of minutes. TeamCity supports Java, .NET and Ruby development and integrates perfectly with major IDEs, version control systems, and issue tracking systems.

    Sample Customers
    Verizon, Cerner, Zipcar, Avarteq
    Toyota, Xerox, Apple, MIT, Volkswagen, HP, Twitter, Expedia
    Top Industries
    VISITORS READING REVIEWS
    Financial Services Firm18%
    Comms Service Provider13%
    Computer Software Company12%
    Government10%
    REVIEWERS
    Financial Services Firm14%
    Computer Software Company14%
    Leisure / Travel Company7%
    Non Tech Company7%
    VISITORS READING REVIEWS
    Financial Services Firm22%
    Computer Software Company14%
    Manufacturing Company10%
    Comms Service Provider7%
    Company Size
    VISITORS READING REVIEWS
    Small Business17%
    Midsize Enterprise10%
    Large Enterprise74%
    REVIEWERS
    Small Business38%
    Midsize Enterprise15%
    Large Enterprise46%
    VISITORS READING REVIEWS
    Small Business24%
    Midsize Enterprise10%
    Large Enterprise66%
    Buyer's Guide
    Build Automation
    March 2024
    Find out what your peers are saying about GitLab, Jenkins, Google and others in Build Automation. Updated: March 2024.
    765,386 professionals have used our research since 2012.

    Concourse for VMware Tanzu is ranked 15th in Build Automation with 1 review while TeamCity is ranked 6th in Build Automation with 24 reviews. Concourse for VMware Tanzu is rated 7.0, while TeamCity is rated 8.4. The top reviewer of Concourse for VMware Tanzu writes "This solution is scalable and stable, but needs more support for deployments outside of Cloud Foundry". On the other hand, the top reviewer of TeamCity writes "Build management system used to successfully create full request tests and run security scans". Concourse for VMware Tanzu is most compared with Jenkins, Tekton, GitLab, Bamboo and Harness, whereas TeamCity is most compared with GitLab, CircleCI, Jenkins and Harness.

    See our list of best Build Automation vendors.

    We monitor all Build Automation reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.