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."The most valuable features are compiling and deployment."
"Bamboo's integration with the rest of Atlassian's tech tools, like Jira, helps manage the end-to-end development and release process."
"The most valuable feature of Bamboo is that it is a good tool for CI/CD integration."
"In my experience Bamboo is scalable."
"It's one of the best solutions in this line of work. We have many Atlassian products. We use Bamboo, JIRA, Service Desk, and some other Atlassian plugins. We like that it's easy to integrate into each other. It's a suite of services."
"The platform helps us with automated and timely backup. It provides data replication as 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."
"One of the big things that made us choose Bamboo, is it seamlessly integrates its APIs into NetSuite, which is our main ELP system."
"One of the most beneficial features for us is the flexibility it offers in creating deployment steps tailored to different technologies."
"Good integration with IDE and JetBrains products."
"TeamCity is very useful due to the fact that it has a strong plug-in system."
"The flexibility of TeamCity allows it to fit in workflows that I have yet to imagine."
"VCS Trigger: Provides excellent source control support."
"TeamCity's GUI is nice."
"It provides repeatable CI/CD throughout our company with lots of feedback on failures and successes to the intended audiences via email and Slack."
"I have not yet implemented the remote build feature, but this will be a big plus. We want to be able to build legacy products on a build agent without developers needing to have obsolete tool sets installed on their local PC."
"Bamboo is a bit complicated to use compared to other solutions, such as GitLab. You have to integrate different actions that are difficult that could be made easier."
"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 solution needs to support more customization in the training. What's offered is pretty generic. They need better training and should offer more guidance."
"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."
"Bamboo can improve by providing more with scripting, such as they have with Jenkins. Bamboo is more UI-driven at this time, Jenkins is going in that direction too."
"It's a little outdated. It's three years old."
"It should be much easier to use. It shouldn't require a lot of reading to be able to use it. It should have just two or three screens rather than hundreds of screens requiring a lot of clicking. It also requires a lot of integration. It has a steep learning curve. It takes a lot of time to understand and put in the data. There is also no proper training."
"The marketing strategy of Bamboo is an area of concern where improvements are needed."
"It will benefit this solution if they keep up to date with other CI/CD systems out there."
"REST API support lacks many features in customization of builds, jobs, and settings."
"If there was more documentation that was easier to locate, it would be helpful for users."
"I need some more graphical design."
"Last time I used it, dotnet compilation had to be done via PowerShell scripts. There was actually a lot that had to be scripted."
"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."
"The upgrade process could be smoother. Upgrading major versions can often cause some pain."
"Integrating with certain technologies posed challenges related to time and required support from the respective technology teams to ensure smooth integration with TeamCity."
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, GitHub Actions 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.