We performed a comparison between Digital.ai Release , Jenkins, and TeamCity based on real PeerSpot user reviews.
Find out what your peers are saying about GitLab, Jenkins, Amazon Web Services (AWS) and others in Build Automation."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 solution can apply one template across multiple applications."
"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."
"Has a good interface, is reliable and saves time."
"A lot of support material exists via a single web search of exactly what you're looking for."
"We can schedule anything with Jenkins, which is useful for deployment or anything that requires scheduling. It also has multiple plugins we can use for Maven, JUnit, etc."
"The most valuable feature is its ability to connect with different tools and technologies."
"The most valuable features are Jenkins Pipelines for ALM and full Deploy Cycle."
"Has enabled full automation of the company."
"Jenkins is very user-friendly."
"This is a great integration tool and very powerful."
"The flexibility of TeamCity allows it to fit in workflows that I have yet to imagine."
"TeamCity is a very user-friendly tool."
"Good integration with IDE and JetBrains products."
"VCS Trigger: Provides excellent source control support."
"It's easy to move to a new release because of templates and meta-runners, and agent pooling."
"We would like to see better integration with other version controls, since we encountered difficulty when this we first attempted."
"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 most valuable aspect of the solution is its easy configuration. It also has multiple plugins that can be used especially for building .net applications."
"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 scriptwriting process could be improved in this solution in the future."
"The support for the latest Java Runtime Environment should be improved."
"Developer documentation for plugins, plugin development, integrations: Sometimes it’s tricky to do pretty obvious things."
"There is no way for the cloud repositories to trigger Jenkins."
"This solution would be improved with the inclusion of an Artifactory (Universal artifact repository manager)."
"A more user-friendly UI for creating pipelines would be helpful."
"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."
"Jenkins can be improved, but it's difficult for me to explain. The initial setup could be more straightforward. If you connect Jenkins with bookings and lockouts, it can be challenging."
"I would suggest creating simple and advanced configurations. Advanced configurations will give more customizations like Jenkins does."
"Last time I used it, dotnet compilation had to be done via PowerShell scripts. There was actually a lot that had to be scripted."
"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."
"If there was more documentation that was easier to locate, it would be helpful for users."
"I need some more graphical design."
"It will benefit this solution if they keep up to date with other CI/CD systems out there."
"The upgrade process could be smoother. Upgrading major versions can often cause some pain."
"Integrating with certain technologies posed challenges related to time and required support from the respective technology teams to ensure smooth integration with TeamCity."
