We performed a comparison between Inedo BuildMaster and TeamCity based on real PeerSpot user reviews.
Find out what your peers are saying about GitLab, Jenkins, Google and others in Build Automation."Technical support is quick to respond. I haven't had any issues with them."
"Time to deployment has been reduced in situations where we want to deploy to production or deploy breaking changes."
"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."
"It provides repeatable CI/CD throughout our company with lots of feedback on failures and successes to the intended audiences via email and Slack."
"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."
"VCS Trigger: Provides excellent source control support."
"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."
"The documentation should be better. It should be very easy to call REST APIs, and the documentation has to be perfect for that."
"Last time I used it, dotnet compilation had to be done via PowerShell scripts. There was actually a lot that had to be scripted."
"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 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."
"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."
"Integrating with certain technologies posed challenges related to time and required support from the respective technology teams to ensure smooth integration with TeamCity."
"It will benefit this solution if they keep up to date with other CI/CD systems out there."
"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."
Inedo BuildMaster is ranked 21st in Build Automation with 1 review while TeamCity is ranked 6th in Build Automation with 25 reviews. Inedo BuildMaster is rated 6.0, while TeamCity is rated 8.2. The top reviewer of Inedo BuildMaster writes "Deployment agent that allows us to deploy out to various other servers but doesn't provide build automation". On the other hand, the top reviewer of TeamCity writes "Build management system used to successfully create full request tests and run security scans". Inedo BuildMaster is most compared with , whereas TeamCity is most compared with GitLab, CircleCI, Jenkins, Harness and Tekton.
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.
