Digital.ai Release vs Jenkins comparison

"The solution can apply one template across multiple applications."

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

"The orchestration, building the release, and then just executing it and managing that pipeline — the orchestration capabilities are great for that."

"It's a powerful tool for CI/CD."

"Continuous Integration. Jenkins can integrate with almost any systems used for application development and testing, with its plugins."

"I like the business logs. It's a very useful tool. Client-server communication is also very fast."

"Jenkins is particularly valuable since it saves time by automating manual tasks."

"Jenkins's automation and orchestration features have significantly improved workflows by automating various processes. Initially, it did not support YAML manifesting or GitOps, but recent versions have introduced these capabilities. Now, the tool supports importing manifest files from Git repositories, enabling the implementation of GitOps pipelines. Compared to other tools like GitLab, it has become a mature tool for running CI/CD pipelines."

"Different types of jobs, such as Pipeline, Build, Freestyle, Maven, etc."

"It is very useful for us to be able to collect and manage automatic processing pipelines."

"Jenkins' most valuable feature is Pipeline."

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

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

"The solution is a little bit expensive."

"The enterprise version is less stable than the open-source version."

"The UI of Jenkins could improve."

"I think an integrated help button, that respected the context of the change/work in hand, would be a worthwhile improvement."

"Jenkins can improve by continuing to add additional plugins for all the new solutions that are coming out within the cloud sphere."

"In our case, we have several products built using Jenkins. It is quite difficult to navigate into the latest stable build in a given OS."

"Sometimes, random errors of metadata are not there, which causes delays. These are essentially gaps in the information being passed to the job."

"The major drawback with Jenkins is the lack of support."

"Jenkins can sometimes run slow, especially when restarting after a plugin installation or when returning from a pipeline view to the dashboard."

"Overall, the price is just too high; especially considering we're in the middle of a pandemic."

"The solution's license includes all features."

"It is a cheap solution."

"It could be cheaper because there are many solutions available in the market. We are paying yearly."

"I used the free OSS version all the time. It was enough for all my needs."

"We are using the free version of Jenkins. There are no costs or licensing."

"​It is free.​"

"Jenkins is not expensive and reasonably priced."

"It's free software with a big community behind it, which is very good."

"Jenkins is open source."