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

Digital.ai Release vs Jenkins 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 (7th)
Jenkins
Ranking in Build Automation
4th
Average Rating
8.0
Reviews Sentiment
7.0
Number of Reviews
92
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of January 2026, in the Build Automation category, the mindshare of Digital.ai Release is 1.8%, up from 0.8% compared to the previous year. The mindshare of Jenkins is 7.5%, down from 11.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation Market Share Distribution
ProductMarket Share (%)
Jenkins7.5%
Digital.ai Release1.8%
Other90.7%
Build Automation
 

Featured Reviews

Jeanne-Mari Chandran - PeerSpot reviewer
Software Configuration Specialist at a insurance company with 10,001+ employees
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.
JI
Principal Software Engineer at a financial services firm with 5,001-10,000 employees
Efficient resource allocation and robust workflow with autoscaling capabilities
In Kubernetes, we use node-based architecture with nodes and pods and follow practices like RBAC and rollback. Multiple pods can run concurrently. We benefit from Kubernetes' ability to autoscale pods and use horizontal pod autoscalers to adjust the number of pods based on metrics like CPU or memory usage, ensuring efficient resource allocation and stability under load.

Quotes from Members

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

Pros

"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."
"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 orchestration, building the release, and then just executing it and managing that pipeline — the orchestration capabilities are great for that."
"The solution can apply one template across multiple applications."
"I like the business logs. It's a very useful tool. Client-server communication is also very fast."
"The most valuable aspect of this solution is that there are multiple features. We can abstract certain variables and then build our deployment routine while being able to do some abstraction onto the SSH connections."
"The initial setup is pretty simple."
"We used it for all continuous integration parts, like automation testing, deployment, etc."
"It is easy to use."
"The most valuable features are Jenkins Pipelines for ALM and full Deploy Cycle."
"It's very useful when you want to automate different processes from beginning to end."
"We use Jenkins to automatically build Python binaries into several OS's i.e. OS X, Ubuntu, Windows 32-bit and Windows 64-bit."
 

Cons

"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 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."
"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."
"There are a lot of things that they can try to improvise. They can reduce a lot of configurations. It is currently supporting Groovy for scripting. It would be really good if it can be improvised for Python because, for most of the automation, we have Python as a script. It would be good if can also support Python. We have a lot of Android builds. These Android builds can be a part of Jenkins. It can have some plug-ins or configurations for Android builds. There should also be some internal matrix to check the performance. We also want to have more REST API support, which is currently not much in Jenkins. We are not able to get more information about running Jenkins. More REST API support should be provided."
"The upgrades need improvement."
"There is no way for the cloud repositories to trigger Jenkins."
"Jenkins could improve by allowing more scripting languages. We need to use Groovy scripting and it is difficult to debug and it is not ideal for creating file scripts. We tried to search for assistance but we did not find much help."
"Creating a new SonarQube project requires a separate job, and we've encountered some integration issues with Docker and the need for better vulnerability checks."
"It can be improved by including automated mobile reporting integrations."
"The support for the latest Java Runtime Environment should be improved."
"I would like to have an integrated dashboard on top of it and a better UX to look at. The dashboard could be better in terms of integration with other tools. We should be able to have a single pane of glass across all the tools that we use where Jenkins is the pipeline. This can be a very good upgrade to it."
 

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."
"This is an open-source solution for the basic features. However, if an organization wishes to include specific functionality, outside of the basic package, there are extra costs involved."
"Jenkins is not expensive and reasonably priced."
"The open-source version is free, but small companies would not be able to afford the cloud-based version."
"There is no cost. It is open source."
"Jenkins is a free solution, it is open source."
"Jenkins is a free open-source server."
"It could be cheaper because there are many solutions available in the market. We are paying yearly."
"The tool is open-source."
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
881,114 professionals have used our research since 2012.
 

Comparison Review

it_user184734 - PeerSpot reviewer
Systems Administrator at Facebook
Jan 22, 2015
I generally find TeamCity a lot more intuitive than Jenkins.
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…
 

Top Industries

By visitors reading reviews
Financial Services Firm
29%
Computer Software Company
11%
Insurance Company
11%
Healthcare Company
10%
Financial Services Firm
20%
Manufacturing Company
14%
Computer Software Company
9%
Government
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business28
Midsize Enterprise15
Large Enterprise56
 

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 ...
How does Tekton compare with Jenkins?
When you are evaluating tools for automating your own GitOps-based CI/CD workflow, it is important to keep your requirements and use cases in mind. Tekton deployment is complex and it is not very e...
What do you like most about Jenkins?
Jenkins has been instrumental in automating our build and deployment processes.
What is your experience regarding pricing and costs for Jenkins?
Jenkins is used in many companies to save money, especially within R&D divisions, by avoiding the expenses of proprietary tools.
 

Comparisons

 

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
Airial, Clarus Financial Technology, cubetutor, Metawidget, mysocio, namma, silverpeas, Sokkva, So Rave, tagzbox
Find out what your peers are saying about Digital.ai Release vs. Jenkins and other solutions. Updated: December 2025.
881,114 professionals have used our research since 2012.