Digital.ai Release vs Jenkins comparison

Cancel
You must select at least 2 products to compare!
Digital.ai Logo
774 views|419 comparisons
100% willing to recommend
Jenkins Logo
6,896 views|5,921 comparisons
88% willing to recommend
Comparison Buyer's Guide
Executive Summary

We performed a comparison between Digital.ai Release and Jenkins 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. Jenkins Report (Updated: March 2024).
767,667 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 orchestration, building the release, and then just executing it and managing that pipeline — the orchestration capabilities are great for that.""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 solution can apply one template across multiple applications."

More Digital.ai Release Pros →

"The initial setup is simple.""Automation of chores like deployment, frequent manual tasks (like running scripts on test and production systems) reduced the time used and the number of errors made by engineers, freeing them to do meaningful work instead.""Jenkins is very user-friendly.""Jenkins has a lot of built-in packages and tools.""The most valuable features are Jenkins Pipelines for ALM and full Deploy Cycle.""With Jenkins, the pipeline will take your code from any versioning system like GitHub or Bitbucket. All the security scans can happen in one go and then all the tests also get run. You can just build one container in it and deploy it.""Having builds and test tasks triggered on commit helps not to break the product.""Continuous Integration. Jenkins can integrate with almost any systems used for application development and testing, with its plugins."

More Jenkins Pros →

Cons
"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.""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."

More Digital.ai Release Cons →

"For this solution to be a 10, it has to be a lot more stable. Maybe the public version of Jenkins is stable, but in our case it's not stable.""This solution could be improved by removing the storage of unnecessary data such as the history of test deployments that were unsuccessful.""We need more licensed product integrations.""Jenkins could simplify the user interface a little bit because it sometimes creates too many features cramped in the UI.""Some kind of SaaS product would be helpful in providing organizational structure.""The bug fix speed is very slow.""I would like them to provide space for people to have a central node that stores all the logs of workspace information in a distributed fashion to facilitate backup and restoration. Currently, everything is stored on one node, so you need to set up distributed storage or an endpoint that you can use for backing up your information.""There are some difficulties when we need to execute the DB script."

More Jenkins 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 →

  • "It is a free product."
  • "Jenkins is open source."
  • "​It is free.​"
  • "Some of the add-ons are too expensive."
  • "It's free software with a big community behind it, which is very good."
  • "I used the free OSS version all the time. It was enough for all my needs."
  • "Jenkins is open source and free."
  • "There is no cost. It is open source."
  • More Jenkins Pricing and Cost Advice →

    report
    Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
    767,667 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: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 easy… more »
    Top Answer:Jenkins has been instrumental in automating our build and deployment processes.
    Ranking
    10th
    out of 41 in Build Automation
    Views
    774
    Comparisons
    419
    Reviews
    2
    Average Words per Review
    621
    Rating
    9.0
    2nd
    out of 41 in Build Automation
    Views
    6,896
    Comparisons
    5,921
    Reviews
    39
    Average Words per Review
    386
    Rating
    7.8
    Comparisons
    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.

    Jenkins is an award-winning application that monitors executions of repeated jobs, such as building a software project or jobs run by cron.

    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
    Top Industries
    VISITORS READING REVIEWS
    Educational Organization45%
    Financial Services Firm20%
    Computer Software Company10%
    Insurance Company4%
    REVIEWERS
    Financial Services Firm33%
    Computer Software Company23%
    Media Company9%
    Comms Service Provider9%
    VISITORS READING REVIEWS
    Financial Services Firm20%
    Computer Software Company17%
    Manufacturing Company11%
    Government6%
    Company Size
    VISITORS READING REVIEWS
    Small Business6%
    Midsize Enterprise48%
    Large Enterprise46%
    REVIEWERS
    Small Business27%
    Midsize Enterprise16%
    Large Enterprise58%
    VISITORS READING REVIEWS
    Small Business17%
    Midsize Enterprise11%
    Large Enterprise72%
    Buyer's Guide
    Digital.ai Release vs. Jenkins
    March 2024
    Find out what your peers are saying about Digital.ai Release vs. Jenkins and other solutions. Updated: March 2024.
    767,667 professionals have used our research since 2012.

    Digital.ai Release is ranked 10th in Build Automation with 3 reviews while Jenkins is ranked 2nd in Build Automation with 83 reviews. Digital.ai Release is rated 8.6, while Jenkins is rated 8.0. 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 Jenkins writes "A highly-scalable and stable solution that reduces deployment time and produces a significant return on investment". Digital.ai Release is most compared with Microsoft Azure DevOps, Bamboo, IBM Rational Build Forge, Digital.ai Deploy and GitLab, whereas Jenkins is most compared with GitLab, Bamboo, AWS CodePipeline, IBM Rational Build Forge and Chef. See our Digital.ai Release vs. Jenkins 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.