Digital.ai Release vs GitHub Actions comparison

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

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

"GitHub Actions can be easily configured, especially for environment variables and secrets. The UI is understandable and user-friendly for setting up CI/CD pipelines. I prefer tools like GitLab, where the pipeline starts quickly and is accessible near the commits for easy access. However, many CI/CD tools are interchangeable due to similar features of GitHub Actions and other similar tools."

"GitHub Actions is a beautiful tool that integrates smoothly with all major tools, reducing CI/CD work by 30% to 40%."

"We can trigger files manually or automate processes."

"The most valuable features of GitHub Actions include its seamless integration within GitHub, which simplifies the CI/CD pipeline setup. The scalability of using different types of runners—both public and private runners—enhances deployment flexibility."

"The most valuable feature of GitHub Actions is the ability to automate various tasks, such as backups and deployments, to ease the development workflow."

"The level of automation achievable is really good. So, the custom workflow creation and Marketplace Actions improved our project's efficiency."

"The product's most beneficial feature is the ability to create workflows within the solution."

"I am familiar with the entire life cycle of the product."

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

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

"The main challenge I've experienced is with integration, particularly uploading to OneDrive, which was more complex compared to Google Drive or AWS S3 bucket."

"The solution's integration capabilities and UI are areas of concern where improvement is required to make the product more user-friendly."

"Sometimes incremental steps should be taken during deployment instead of trying to execute all tasks simultaneously, particularly when dealing with AWS EKS clusters and Helm charts."

"The UI could be better."

"In our company, procedures or rules need to be completed, which is not a problem with GitHub Actions but with our process."

"We can leverage this database tool to manage everything within our environment and data burners, allowing for customization and execution. An additional advantage is the capability to modify aspects like file size, making processes more efficient and faster across the pipelines. Regarding improvements or implementations, I believe there should be enhancements made to the deployment tool. It should be integrated as part of the solution. Infrastructure-wise, we already have tools like GitHub and RobSpot, and data enables us to automate various processes, which is quite beneficial. As for further enhancements, I'm uncertain. I've shared everything I know. However, if there's something specific you'd like to see in future releases, a feature that may not exist yet but would be desirable, I can't provide any input on that matter."

"The primary area for improvement I see is in artifact management, especially for saving screenshots or videos from failed tests or data-driven actions. Currently, the configuration for saving these artifacts is complex."

"My company would want to see some AI features in the tool as it can add value to the product."

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

"The solution's license includes all features."

"Price-wise, GitHub Actions is okay. If I want to use the product's advanced features, then I need to pay the licensing charges for the solution."

"The tool's price is okay and reasonable."

"It's low-priced. Not high, but definitely low."

"Regarding cost, as an enterprise, we negotiate our license and expenses, so I can't provide a specific rating for that."

"It is free and open platform, so I would rate it 1 out of 10."

"For our basic usage, we didn't have to pay."

"The cost for GitHub Actions may be around $45 dollars per user."

"The product is slightly more expensive than some alternatives."