We performed a comparison between AWS CodePipeline 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."I find performance to be the most valuable CodePipeline feature. It works perfectly and smoothly."
"The product is cost-effective and integrates well with the AWS environment."
"The product is a one-stop solution that you can use to integrate, deploy and host your application."
"In AWS, the Cloud DevOps is a managed service from CodeCommit and this has removed the need for a lot of manual steps."
"It's a perfect solution if you are just using AWS."
"It helps develop CI/CD implementations with centralized management of code building, deployment, and version control."
"AWS CodePipeline has valuable integration features."
"The most valuable feature of AWS CodePipeline is the flexibility of the configuration."
"The most valuable feature of the solution is its integration between different tools."
"We used it for all continuous integration parts, like automation testing, deployment, etc."
"I like that you can find a wide range of plugins for Jenkins."
"The most valuable feature of Jenkins is its open source."
"It is a stable solution."
"It can scale easily."
"This solution has helped us in automating the build and test process, reducing time."
"Jenkins has excellent task planning features."
"In the next release, I would like to see fewer timeout errors."
"The setup time is a bit long."
"There could be a possibility of deploying tag-based conditions for different environments using the same code base."
"The migration process from one source code to another needs improvement."
"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."
"If you're talking about multi-cloud, you can't use it."
"AWS CodePipeline doesn't offer much room for customization."
"Jenkins could improve by allowing more scripting languages. We need to use Groovy scripting and it is difficult to debug and it is not ideal for creating file scripts. We tried to search for assistance but we did not find much help."
"It does not have a very user-friendly interface."
"The onboarding of Jenkins should be smoother, and it should have more pipelines available as it's deployed on many different servers."
"The user interface could be updated a little."
"The enterprise version is less stable than the open-source version."
"Logging could be improved to offer a clearer view."
"Developer documentation for plugins, plugin development, integrations: Sometimes it’s tricky to do pretty obvious things."
"Its schedule builds need improvement. It should have scheduling features in the platform rather than using external plug-ins."
AWS CodePipeline is ranked 4th in Build Automation with 10 reviews while Jenkins is ranked 2nd in Build Automation with 83 reviews. AWS CodePipeline is rated 8.4, while Jenkins is rated 8.0. 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 Jenkins writes "A highly-scalable and stable solution that reduces deployment time and produces a significant return on investment". AWS CodePipeline is most compared with GitLab, AWS CodeStar, Tekton, GitHub Actions and Bamboo, whereas Jenkins is most compared with GitLab, Bamboo, IBM Rational Build Forge, Tekton and Harness. See our AWS CodePipeline 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.