Bamboo vs TeamCity comparison

Cancel
You must select at least 2 products to compare!
Atlassian Logo
3,414 views|3,401 comparisons
75% willing to recommend
JetBrains Logo
3,373 views|2,977 comparisons
92% willing to recommend
Comparison Buyer's Guide
Executive Summary

We performed a comparison between Bamboo and TeamCity based on real PeerSpot user reviews.

Find out in this report how the two Build Automation solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI.
To learn more, read our detailed Bamboo vs. TeamCity Report (Updated: March 2024).
768,246 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
"The most valuable features are compiling and deployment.""The most useful feature of Bamboo is its integration with other solutions such as Jira and BitBucket, also offered by Atlassian. It is easier to use tools all provided by one vendor.""Bamboo was used extensively in our organization for PCA compliance.""The most valuable feature of Bamboo is that it is a good tool for CI/CD integration.""In Bamboo, build and deployment have been segregated. The build plan and deployment plan are different. When comparing Bamboo to other solutions, the native feature you will not find in another tool, such as Jenkins. They have segregated the build and deployment plan. This means, building the application and deploying it are two separate parts in Bamboo, they have segregated it apart from the UI. This makes the tool a bit better compared to other tools.""One of the significant benefits of Bamboo is its built-in support for numerous clients and the ability to tailor its capabilities to your specific requirements. This high level of customization enables you to create pipelines that are ideally suited to your needs, making it an invaluable tool for conducting advanced testing.""It can do the CI pipeline well.""The most valuable features of Bamboo are its performance and UI. Additionally, there are a lot of useful plugins, integration with other solutions, such as Bitbucket and Jira, and a helpful online community."

More Bamboo Pros →

"We would like to see better integration with other version controls, since we encountered difficulty when this we first attempted.""TeamCity is a very user-friendly tool.""One of the most beneficial features for us is the flexibility it offers in creating deployment steps tailored to different technologies.""It provides repeatable CI/CD throughout our company with lots of feedback on failures and successes to the intended audiences via email and Slack.""It's easy to move to a new release because of templates and meta-runners, and agent pooling.""Time to deployment has been reduced in situations where we want to deploy to production or deploy breaking changes.""VCS Trigger: Provides excellent source control support.""The flexibility of TeamCity allows it to fit in workflows that I have yet to imagine."

More TeamCity Pros →

Cons
"It can be challenging for someone new to the system or ecosystem to grasp, making it difficult to train new people and help them understand.""The marketing strategy of Bamboo is an area of concern where improvements are needed.""One area that could be enhanced is the governance process, particularly with regard to building approvals and transitions between stages. In comparison to other solutions, such as Jira, which features a workflow that supports approval processes, this capability is not natively available in Bamboo. To implement this functionality, integration with other solutions, such as GSM may be necessary. Although some add-ons, such as Adaptavist ScriptRunner, are available in the market to circumvent this limitation, they may not offer the exact functionality needed. Therefore, there is certainly room for improvement in this area.""The performance around the deployment feature could be improved.""It's a little outdated. It's three years old.""The solution needs to support more customization in the training. What's offered is pretty generic. They need better training and should offer more guidance.""Bamboo’s technical support services, in terms of speed of response, need improvement.""It would be great if Bamboo could introduce a more containerized deployment model."

More Bamboo Cons →

"The upgrade process could be smoother. Upgrading major versions can often cause some pain.""REST API support lacks many features in customization of builds, jobs, and settings.""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.""It will benefit this solution if they keep up to date with other CI/CD systems out there.""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.""Integrating with certain technologies posed challenges related to time and required support from the respective technology teams to ensure smooth integration with TeamCity.""If there was more documentation that was easier to locate, it would be helpful for users."

More TeamCity Cons →

Pricing and Cost Advice
  • "There is a subscription required to use Bamboo."
  • "If Bamboo could provide more flexibility on pricing, that would help. On the agent side, if you want to increase the number of agents it should be less expensive. If they can provide some better pricing model, it will help, whether we are going to use it or are already using it."
  • "The server products for small teams used to offer excellent pricing. However, Atlassian has since changed the offering and the pricing is more expensive. I do still think the solution offers good value for money."
  • "The price of Bamboo is reasonable."
  • "I rate the product’s pricing a five out of ten."
  • More Bamboo 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.
    768,246 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:Bamboo's integration with the rest of Atlassian's tech tools, like Jira, helps manage the end-to-end development and release process.
    Top Answer:I rate the product’s pricing a five out of ten.
    Top Answer:The tools and capabilities of the system are extensive. It can be challenging for someone new to the system or ecosystem to grasp, making it difficult to train new people and help them understand.
    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
    5th
    out of 41 in Build Automation
    Views
    3,414
    Comparisons
    3,401
    Reviews
    7
    Average Words per Review
    542
    Rating
    7.7
    6th
    out of 41 in Build Automation
    Views
    3,373
    Comparisons
    2,977
    Reviews
    2
    Average Words per Review
    574
    Rating
    8.0
    Comparisons
    GitLab logo
    Compared 43% of the time.
    Jenkins logo
    Compared 22% of the time.
    GitHub Actions logo
    Compared 7% of the time.
    Harness logo
    Compared 7% of the time.
    AWS CodePipeline logo
    Compared 3% of the time.
    GitLab logo
    Compared 44% of the time.
    CircleCI logo
    Compared 17% of the time.
    Jenkins logo
    Compared 9% of the time.
    Harness logo
    Compared 6% of the time.
    AWS CodePipeline logo
    Compared 2% of the time.
    Learn More
    Overview
    Bamboo is a continuous integration and delivery tool that ties automated builds, tests and releases together in a single workflow. It works great alongside JIRA and Stash providing a fully traceable deployment pipeline.

    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
    Neocleus, MuleSoft, Interspire
    Toyota, Xerox, Apple, MIT, Volkswagen, HP, Twitter, Expedia
    Top Industries
    REVIEWERS
    Computer Software Company40%
    Financial Services Firm20%
    Marketing Services Firm10%
    Non Tech Company10%
    VISITORS READING REVIEWS
    Financial Services Firm18%
    Manufacturing Company14%
    Computer Software Company13%
    Government8%
    REVIEWERS
    Financial Services Firm13%
    Computer Software Company13%
    Non Tech Company7%
    Hospitality Company7%
    VISITORS READING REVIEWS
    Financial Services Firm21%
    Computer Software Company15%
    Manufacturing Company10%
    Comms Service Provider7%
    Company Size
    REVIEWERS
    Small Business30%
    Midsize Enterprise30%
    Large Enterprise40%
    VISITORS READING REVIEWS
    Small Business15%
    Midsize Enterprise14%
    Large Enterprise71%
    REVIEWERS
    Small Business37%
    Midsize Enterprise15%
    Large Enterprise48%
    VISITORS READING REVIEWS
    Small Business25%
    Midsize Enterprise9%
    Large Enterprise66%
    Buyer's Guide
    Bamboo vs. TeamCity
    March 2024
    Find out what your peers are saying about Bamboo vs. TeamCity and other solutions. Updated: March 2024.
    768,246 professionals have used our research since 2012.

    Bamboo is ranked 5th in Build Automation with 20 reviews while TeamCity is ranked 6th in Build Automation with 25 reviews. Bamboo is rated 7.4, while TeamCity is rated 8.2. The top reviewer of Bamboo writes "High availability, helpful support, and plenty of plugins available". On the other hand, the top reviewer of TeamCity writes "Build management system used to successfully create full request tests and run security scans". Bamboo is most compared with GitLab, Jenkins, GitHub Actions, Harness and AWS CodePipeline, whereas TeamCity is most compared with GitLab, CircleCI, Jenkins, Harness and AWS CodePipeline. See our Bamboo vs. TeamCity report.

    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.