We performed a comparison between AWS CodePipeline and GitHub Actions 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."The product is cost-effective and integrates well with the AWS environment."
"The tool's recent version helps us to run pipelines in parallel. The integration with other AWS services has greatly impacted our use of AWS CodePipeline. It made tasks such as integrating with Jira and provisioning instances much easier."
"The integrations are good."
"The integration with other applications is fabulous."
"AWS CodePipeline has valuable integration features."
"It's a perfect solution if you are just using AWS."
"AWS CodePipeline offers multiple integrations and it has its own set of features in the area of code scanning and dynamic code testing."
"The product is a one-stop solution that you can use to integrate, deploy and host your application."
"The level of automation achievable is really good. So, the custom workflow creation and Marketplace Actions improved our project's efficiency."
"I have optimized job execution time by running test scripts in parallel and creating multiple pipelines; we've significantly reduced execution times. What could take 50 minutes can be cut down to just 8 to 10 minutes through these optimizations."
"The main benefit is collaboration. It allows us to easily collaborate with other developers, regardless of location. For example, we can collaborate with both our African and German colleagues seamlessly. It's platform-agnostic, so it is flexible and not tied to any OS, so we can work on Linux, Windows, web, and even Oracle applications. It's flexible, reliable, and overall an excellent tool for our needs."
"It offers numerous built-in features for pipeline management, release management, and even work item tracking on boards, which makes it a versatile tool that seamlessly integrates with hardware and facilitates optimization."
"Creating workflows in YAML format is straightforward and easy to comprehend. This includes both understanding and writing workflows. Additionally, the downloading aspect for third-party instances can also be easily done. It's worth noting that vulnerability analysis and similar tasks should be part of our automation through data workflows. Furthermore, we can break down our processes step by step, starting from building, then moving on to analysis, testing, and finally deploying in production and the clear environment. All of these tasks can be efficiently managed within this platform."
"The most valuable feature of the solution is that it is a good product that offers stability and performance."
"The product’s pricing needs improvement."
"The migration process from one source code to another needs improvement."
"The solution could improve the documentation. Sometimes we have some issues with the documentation not updating after releasing .NET 6. We had some issues with building the code pipeline, and it was not updating the documentation. It's better to update the code documentation."
"If you're talking about multi-cloud, you can't use it."
"If there are many dependancies involved in the setup, it may take a long time."
"The tool does not provide automated features for evidence collection."
"The support team’s response time must be improved."
"There could be a possibility of deploying tag-based conditions for different environments using the same code base."
"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 reporting capabilities are somewhat limited."
"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."
"There is a part that detects outdated libraries. If that feature could be more intuitive and informative, that would be nice."
"The UI could be better."
"The solution's integration capabilities and UI are areas of concern where improvement is required to make the product more user-friendly."
AWS CodePipeline is ranked 3rd in Build Automation with 13 reviews while GitHub Actions is ranked 7th in Build Automation with 6 reviews. AWS CodePipeline is rated 8.4, while GitHub Actions is rated 8.4. The top reviewer of AWS CodePipeline writes "A fully managed service with excellent integrations and a flexible architecture". On the other hand, the top reviewer of GitHub Actions writes "Facilitates connectivity for developers and allows us to easily collaborate with other developers, regardless of location". AWS CodePipeline is most compared with GitLab, AWS CodeStar, Jenkins, Tekton and Bamboo, whereas GitHub Actions is most compared with Tekton, Bamboo, GitLab, TeamCity and Harness. See our AWS CodePipeline vs. GitHub Actions 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.