CloudBees vs. TeamCity

As of June 2019, CloudBees is ranked 2nd in Build Automation with 10 reviews vs TeamCity which is ranked 3rd in Build Automation with 6 reviews. The top reviewer of CloudBees writes "It has drastically improved our workflows and the speed of our troubleshooting". The top reviewer of TeamCity writes "The flexibility of the product allows it to support a seemingly infinite number of build workflows". CloudBees is most compared with Jenkins, Bamboo and TeamCity. TeamCity is most compared with Jenkins, GitLab and Bamboo. See our CloudBees vs. TeamCity report.
Cancel
You must select at least 2 products to compare!
CloudBees Logo
6,445 views|2,868 comparisons
TeamCity Logo
27,839 views|6,151 comparisons
Most Helpful Review
Find out what your peers are saying about CloudBees vs. TeamCity and other solutions. Updated: May 2019.
348,558 professionals have used our research since 2012.
Quotes From Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:

Pros
Key features include ease of access control (granular), scalability, and especially the analytics.It has easy connectivity for getting our pipelines into the cloud on AWS.The integration and configuration of CloudBees in our AWS environment was pretty much plug and play. We have admin rights anytime we need to plug into a new service. We just download a plugin, and it spins up and works.The benefit is support and the speed that it provides for troubleshooting.It makes my job easier and does things that I don't have to do.The quality of our results has gone up and the time devoted on our side has gone down.It has a good reporting solution and a wide variety of plugins.It was easy to integrate into our AWS environment.

Read more »

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.The flexibility of TeamCity allows it to fit in workflows that I have yet to imagine.It provides repeatable CI/CD throughout our company with lots of feedback on failures and successes to the intended audiences via email and Slack.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.It's easy to move to a new release because of templates and meta-runners, and agent pooling.VCS Trigger: Provides excellent source control support.Good integration with IDE and JetBrains products.

Read more »

Cons
There are a lot of features, so some really good learning materials in various formats would be handy. I know there are a lot of webinars, but more high-level resources would be great for new staff.Nothing is perfect, and there is room for improvement in the product. I am reserving judgment for the unknown.I still find the messaging really confusing. It's not immediately clear what the value-add is yet. It's not clear enough to pitch it in an easy, prepackaged way.I am not a fan of Java as a language or a platform, but it comes with the territory.With Kubernetes and the cloud-based configuration, it is a little tricky. We are still trying to figure out the best way to do it.It needs scripting in other languages and support for it.Sometimes on a heavily used Jenkins instance, if we are not scaling appropriately, we can have a lot of job failures without a whole lot of information telling us why jobs are failing, if we don't know that it's a performance issue.I would like to see a more click-through, automatic creation of AML files. Sometimes, we give guides for developers in order to do things, but not all of them are familiar enough with AML, as they are Java developers.

Read more »

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.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.The upgrade process could be smoother. Upgrading major versions can often cause some pain.I would suggest creating simple and advanced configurations. Advanced configurations will give more customizations like Jenkins does.

Read more »

Pricing and Cost Advice
Pricing must be fair because we just renewed our license a couple months ago.Their support model is a recurring model. It is not a one-off fee. We pay on a yearly basis.They need to improve the licensing. With a few of the companies, when you have the agent installed, once the instance dies, you are released from the license. However, with cloud-based, you have to contact the cloud-based support to release the license and map it to the new instance.We chose to go through the AWS Marketplace because of scalability.Since we are on the free, open source, we don't necessarily get access to their private community and other commercial forums. However, the open source community has been fantastic for us.The amount of time that it takes to build software, test it, pass the testing, and get it deployed onto a server instance has dropped for a developer to do all these processes from about a day to a couple of minutes. Where we previously had a developer who might only have only been able to do one build, deployment, and test per day, they can now do dozens before lunch. That is the ROI.Purchasing on the AWS Marketplace was easy. We don't worry about licensing and keeping track of it. We don't worry about negotiating contracts. It just happens. We get the bill, which is billed to our account. It is very painless.The AWS Marketplace pricing is on par with going directly to CloudBees. It's always nice if it is cheaper, but it's on par.

Read more »

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.

Read more »

report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
348,558 professionals have used our research since 2012.
Ranking
2nd
out of 23 in Build Automation
Views
6,445
Comparisons
2,868
Reviews
10
Average Words per Review
745
Avg. Rating
7.7
3rd
out of 23 in Build Automation
Views
27,839
Comparisons
6,151
Reviews
6
Average Words per Review
265
Avg. Rating
8.3
Top Comparisons
Compared 73% of the time.
Compared 6% of the time.
Compared 4% of the time.
Compared 49% of the time.
Compared 15% of the time.
Compared 12% of the time.
Learn
CloudBees
JetBrains
Overview
The CloudBees is the industry's most proven, fully featured technology platform for implementing continuous integration (CI) and continuous delivery (CD). CI and CD help you deliver better software faster by automating the software delivery lifecycle allowing faster delivery of new applications and features to meet the needs of organization. While CI lets you automate the software build, scan and test process, CD automates the full application delivery pipeline taking new features and code from development to staging to production.

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.

Offer
Learn more about CloudBees
Learn more about TeamCity
Sample Customers
Acxiom, ARTstor, Choose Digital, Dominion Marine Media, Egraphs, Inc., Global Bank, jclouds, MovellasToyota, Xerox, Apple, MIT, Volkswagen, HP, Twitter, Expedia
Find out what your peers are saying about CloudBees vs. TeamCity and other solutions. Updated: May 2019.
348,558 professionals have used our research since 2012.
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.

Sign Up with Email