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 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."
"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."
"Bamboo's integration with the rest of Atlassian's tech tools, like Jira, helps manage the end-to-end development and release process."
"The platform helps us with automated and timely backup. It provides data replication as well."
"The most valuable feature of Bamboo is that it is a good tool for CI/CD integration."
"One of the big things that made us choose Bamboo, is it seamlessly integrates its APIs into NetSuite, which is our main ELP system."
"The most valuable features are compiling and deployment."
"It can do the CI pipeline well."
"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."
"Good integration with IDE and JetBrains products."
"The integration is a valuable feature."
"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."
"One of the most beneficial features for us is the flexibility it offers in creating deployment steps tailored to different technologies."
"TeamCity is very useful due to the fact that it has a strong plug-in system."
"It provides repeatable CI/CD throughout our company with lots of feedback on failures and successes to the intended audiences via email and Slack."
"TeamCity's GUI is nice."
"The marketing strategy of Bamboo is an area of concern where improvements are needed."
"Scalability depends on the use case. If it is really a big customer with a lot of tests, it might not be a scalable option for them."
"It would be great if Bamboo could introduce a more containerized deployment model."
"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’s technical support services, in terms of speed of response, need improvement."
"It's a little outdated. It's three years old."
"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 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."
"REST API support lacks many features in customization of builds, jobs, and settings."
"I would suggest creating simple and advanced configurations. Advanced configurations will give more customizations like Jenkins does."
"If TeamCity could create more out of the box solutions to make it more user friendly and create more use cases, that would be ideal."
"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.