Digital.ai Release vs TeamCity comparison

Cancel
You must select at least 2 products to compare!
Digital.ai Logo
739 views|402 comparisons
100% willing to recommend
JetBrains Logo
3,337 views|2,954 comparisons
92% willing to recommend
Comparison Buyer's Guide
Executive Summary

We performed a comparison between Digital.ai Release 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.
To learn more, read our detailed Digital.ai Release vs. TeamCity Report (Updated: May 2024).
769,976 professionals have used our research since 2012.
Featured Review
Quotes From Members
We asked business professionals to review the solutions they use.
Here are some excerpts of what they said:
Pros
"The solution can apply one template across multiple applications.""The orchestration, building the release, and then just executing it and managing that pipeline — the orchestration capabilities are great for that.""The time is also reduced because the manual work has tremendously decreased. We just have to click one button, and it will create everything for us.""The most valuable feature of Digital.ai Release is its ability to communicate with various deployment systems, such as XLD and batch deployments, as well as integrate with tools, such as Flyway and Bamboo. We use Bamboo as our build orchestrator, and Digital.ai Release also integrates with Jira, another Atlassian solution. These capabilities make it a powerful tool for managing workflow, test automation, and other processes."

More Digital.ai Release Pros →

"VCS Trigger: Provides excellent source control support.""Good integration with IDE and JetBrains products.""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.""The flexibility of TeamCity allows it to fit in workflows that I have yet to imagine.""TeamCity's GUI is nice.""TeamCity is a very user-friendly tool."

More TeamCity Pros →

Cons
"Currently, we put artifact details manually. What we could improve, in our case, is the deployment instruction base. Developers input all the information, including which artifact and where it needs to be deployed. What Digital.ai could do is automatically go to the deployment instruction page, take those artifact details, and implement them.""Digital.ai Release could improve by having a better plugin that works with Guardian that we use for mainframe migrations. If there could be an interface or plugin for Guardian that would be beneficial.""The solution is a little bit expensive.""The backfill could be improved, we could automate that. Right now it's subjective — it's up to the lead developer's memory to remember to backfill."

More Digital.ai Release Cons →

"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.""Last time I used it, dotnet compilation had to be done via PowerShell scripts. There was actually a lot that had to be scripted.""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.""I would suggest creating simple and advanced configurations. Advanced configurations will give more customizations like Jenkins does.""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.""I need some more graphical design."

More TeamCity Cons →

Pricing and Cost Advice
  • "Overall, the price is just too high; especially considering we're in the middle of a pandemic."
  • "The solution's license includes all features."
  • More Digital.ai Release Pricing and Cost Advice →

  • "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."
  • "The licensing is on an annual basis."
  • More TeamCity Pricing and Cost Advice →

    report
    Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
    769,976 professionals have used our research since 2012.
    Comparison Review
    Anonymous User
    Moving to TeamCity from Jenkins At work, we’re slowly migrating from Jenkins to TeamCity in the hope of ending some of our recurring problems with continuous integration. My use of Jenkins prior to this job has been almost strictly on a personal basis, although I pretty much only use Travis nowadays. The biggest difference upon initial inspection is that TeamCity is far more focused on validating individual commits rather than certain types of tests. Jenkins’ front page presents information that is simply not useful in a non-linear development environment, where people are often working in vastly different directions. How many of the previous tests passed/failed is not really salient information in this kind of situation. Running specific tests for individual commits on TeamCity is far more trivial in terms of interface complexity than Jenkins. TeamCity just involves clicking the ”…” button in the corner on any test type (although I wish it wasn’t so easy to click “Run” by accident). I generally find TeamCity a lot more intuitive than Jenkins out of the box. There’s a point at which you feel that if you have to scour the documentation to do anything remotely complex in an application, you’re dealing with a bad interface. One disappointing thing in both is that inter-branch merges improperly trigger e-mails to unrelated committers. I suppose it is fairly difficult to determine who to notify about failure in situations like these, though. It seems like TeamCity pulls up the… Read more →
    Questions from the Community
    Top Answer:The solution can apply one template across multiple applications.
    Top Answer:The solution's license includes all features. I have not compared pricing to other tools, but feel the solution is a little expensive.
    Top Answer:The solution is a little bit expensive.
    Top Answer:One of the most beneficial features for us is the flexibility it offers in creating deployment steps tailored to different technologies.
    Top Answer:It's open source, however, if you want your solution to be deployed on their cloud or on the cloud in general without you being involved and having it and managed by them, there may be costs involved… more »
    Top Answer:I haven't faced many challenges or issues that I would like to see improved in TeamCity. As for deployment challenges, they are often tied to the specific technology being integrated with TeamCity. In… more »
    Ranking
    12th
    out of 41 in Build Automation
    Views
    739
    Comparisons
    402
    Reviews
    3
    Average Words per Review
    618
    Rating
    8.3
    6th
    out of 41 in Build Automation
    Views
    3,337
    Comparisons
    2,954
    Reviews
    3
    Average Words per Review
    531
    Rating
    7.3
    Comparisons
    GitLab logo
    Compared 44% of the time.
    CircleCI logo
    Compared 17% of the time.
    Jenkins logo
    Compared 8% of the time.
    Harness logo
    Compared 7% of the time.
    GitHub Actions logo
    Compared 6% of the time.
    Also Known As
    XL Release, XebiaLabs XL Release
    Learn More
    Overview

    Automate, orchestrate, and gain visibility into your release pipelines at scale using Digital.ai Release, a release management tool that is designed for enterprises. Control and track releases, standardize processes, and bake compliance and security into your software release pipelines.

    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.

    Sample Customers
    3M, GE, John Deere, Deutsche Telekom, Cable & Wireless, Xerox, and Société Générale, Liberty Mutual, EA, Rabobank
    Toyota, Xerox, Apple, MIT, Volkswagen, HP, Twitter, Expedia
    Top Industries
    VISITORS READING REVIEWS
    Educational Organization46%
    Financial Services Firm20%
    Computer Software Company10%
    Insurance Company4%
    REVIEWERS
    Financial Services Firm13%
    Computer Software Company13%
    Non Tech Company7%
    Hospitality Company7%
    VISITORS READING REVIEWS
    Financial Services Firm20%
    Computer Software Company15%
    Manufacturing Company10%
    Comms Service Provider8%
    Company Size
    VISITORS READING REVIEWS
    Small Business6%
    Midsize Enterprise49%
    Large Enterprise45%
    REVIEWERS
    Small Business37%
    Midsize Enterprise15%
    Large Enterprise48%
    VISITORS READING REVIEWS
    Small Business25%
    Midsize Enterprise10%
    Large Enterprise65%
    Buyer's Guide
    Digital.ai Release vs. TeamCity
    May 2024
    Find out what your peers are saying about Digital.ai Release vs. TeamCity and other solutions. Updated: May 2024.
    769,976 professionals have used our research since 2012.

    Digital.ai Release is ranked 12th in Build Automation with 4 reviews while TeamCity is ranked 6th in Build Automation with 25 reviews. Digital.ai Release is rated 8.2, while TeamCity is rated 8.2. The top reviewer of Digital.ai Release writes "Effectively automates deployments and applies one template across applications". On the other hand, the top reviewer of TeamCity writes "Build management system used to successfully create full request tests and run security scans". Digital.ai Release is most compared with Jenkins, Microsoft Azure DevOps, IBM Rational Build Forge, GitLab and Bamboo, whereas TeamCity is most compared with GitLab, CircleCI, Jenkins, Harness and GitHub Actions. See our Digital.ai Release 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.