Try our new research platform with insights from 80,000+ expert users

Digital.ai Release vs Travis CI comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Mar 5, 2025

Review summaries and opinions

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

Categories and Ranking

Digital.ai Release
Ranking in Build Automation
15th
Average Rating
8.4
Reviews Sentiment
7.5
Number of Reviews
5
Ranking in other categories
Release Automation (10th), DevSecOps (9th)
Travis CI
Ranking in Build Automation
21st
Average Rating
6.0
Reviews Sentiment
3.1
Number of Reviews
2
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of June 2025, in the Build Automation category, the mindshare of Digital.ai Release is 0.9%, down from 0.9% compared to the previous year. The mindshare of Travis CI is 0.8%, down from 1.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation
 

Featured Reviews

Jeanne-Mari Chandran - PeerSpot reviewer
Experience seamless project management and integration with robust tools
The features I find most valuable in Digital.ai Release are the integration with MS Teams, because we have MS Teams channels that publish or push notifications to that. When we start deployments, it sends a notification to the people that we are doing a deployment to their environment. It notifies them when the deployment is started, completed, or if attention is required. I also appreciate the fact that it has plugins for Bamboo and I use lots of Gradle and JSON scripts, and we do SQL upgrades as well, triggering Flyway scripts via Bamboo, along with the integration with XLD and Jira; it's all Atlassian software. Regarding environment management capabilities, Digital.ai Release is mostly useful for me, as it is more application related and that is managed via my XLD dictionary. We have one artifact that is environment agnostic, which has placeholders that correspond to my XLD keys and values, and at deployment time, it substitutes the placeholders with those environment specific values. We don't need to make a specific deployment artifact for dev, test, or production; it is all the same artifact using environment variables, ensuring what we take to production is what was tested.
Pravar Agrawal - PeerSpot reviewer
YAML-based configuration and simple deployment but user interface needs modernizing
Travis CI is an okay tool, and I am forced to use it as part of my job. I don't maintain it; it is running somewhere else, and I don't have control over it. The interface is very basic and not user-friendly; it feels like it was stuck in 2010. It is very basic and designed for lightweight CI work, and it cannot handle heavy CI. You cannot do branched flows, and you will have to write shell scripts to send calls here and there. The pipelines are not as detailed as some other CI/CD tools. If Travis is down, you don't have any control over it and need to reach out to their customer support.

Quotes from Members

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

Pros

"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."
"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."
"Overall, I would give Digital.ai Release a rating of nine out of ten; there's always room for improvement, but it's really good."
"The solution can apply one template across multiple applications."
"The only thing I like about Travis CI is that you have a YAML file to define a Travis flow."
 

Cons

"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."
"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."
"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."
"I would like to improve Digital.ai Release by exploring its cloud capabilities as we are currently in the middle of migrating to the cloud, but I actually have no idea what Digital.ai's cloud capabilities are."
"The interface is very basic and not user-friendly; it feels like it was stuck in 2010."
 

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."
Information not available
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
857,028 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Educational Organization
35%
Financial Services Firm
27%
Computer Software Company
13%
Government
5%
No data available
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
No data available
 

Questions from the Community

What do you like most about Digital.ai Release ?
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.
What needs improvement with Digital.ai Release ?
Based on my experience, I would like to improve Digital.ai Release by exploring its cloud capabilities as we are currently in the middle of migrating to the cloud, but I actually have no idea what ...
What is your primary use case for Digital.ai Release ?
My use case for Digital.ai Release is that I work for an insurance company on a very big project that develops multiple different pieces of software. We use Digital.ai Release to move our software ...
What is your experience regarding pricing and costs for Travis CI?
I'm not too sure about the pricing of Travis or how the agreement works.
What needs improvement with Travis CI?
Travis CI is an okay tool, and I am forced to use it as part of my job. I don't maintain it; it is running somewhere else, and I don't have control over it. The interface is very basic and not user...
What is your primary use case for Travis CI?
Travis CI is mainly used to run integration tests as part of the deployment, which I do on Kubernetes. The Travis workflows are integrated with any changes in my code. It will have different jobs, ...
 

Also Known As

XL Release, XebiaLabs XL Release
No data available
 

Overview

 

Sample Customers

3M, GE, John Deere, Deutsche Telekom, Cable & Wireless, Xerox, and Société Générale, Liberty Mutual, EA, Rabobank
Facebook, Heroku, Mozilla, Zendesk, twitter, Rails
Find out what your peers are saying about GitLab, Google, Jenkins and others in Build Automation. Updated: June 2025.
857,028 professionals have used our research since 2012.