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."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."
"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."
"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."
"Bamboo's integration with the rest of Atlassian's tech tools, like Jira, helps manage the end-to-end development and release process."
"It can do the CI pipeline 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."
"Bamboo was used extensively in our organization for PCA compliance."
"TeamCity is very useful due to the fact that it has a strong plug-in system."
"TeamCity's GUI is nice."
"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."
"The flexibility of TeamCity allows it to fit in workflows that I have yet to imagine."
"We would like to see better integration with other version controls, since we encountered difficulty when this we first attempted."
"Time to deployment has been reduced in situations where we want to deploy to production or deploy breaking changes."
"The integration is a valuable feature."
"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."
"Bamboo’s technical support services, in terms of speed of response, need improvement."
"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."
"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."
"The performance around the deployment feature could be improved."
"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."
"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."
"It will benefit this solution if they keep up to date with other CI/CD systems out there."
"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."
"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."
"Integrating with certain technologies posed challenges related to time and required support from the respective technology teams to ensure smooth integration with TeamCity."
"The upgrade process could be smoother. Upgrading major versions can often cause some pain."
"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 need some more graphical design."
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 IBM Rational Build Forge, 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.
