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."In AWS, the Cloud DevOps is a managed service from CodeCommit and this has removed the need for a lot of manual steps."
"Code deployment is the best feature."
"AWS CodePipeline offers multiple integrations and it has its own set of features in the area of code scanning and dynamic code testing."
"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 most valuable feature of AWS CodePipeline is the flexibility of the configuration."
"AWS CodePipeline has valuable integration features."
"I find performance to be the most valuable CodePipeline feature. It works perfectly and smoothly."
"The integration with other applications is fabulous."
"The most valuable feature is its ability to connect with different tools and technologies."
"We really appreciate that this solution is plug and play. When coding in the version control system, this product completes the build process automatically."
"The most valuable features of Jenkins are the integration of automatic scripts for testing and the user's ability to use any script."
"Jenkins has been instrumental in automating our build and deployment processes."
"I love Jenkins. I like that you work on anything, and you make anything. Jenkins is very important for my team. I am satisfied with the product."
"The solution is scalable and concurrent users have access to the platform."
"Having builds and test tasks triggered on commit helps not to break the product."
"The most valuable aspect of this solution is that there are multiple features. We can abstract certain variables and then build our deployment routine while being able to do some abstraction onto the SSH connections."
"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."
"The setup time is a bit long."
"If there are many dependancies involved in the setup, it may take a long time."
"The migration process from one source code to another needs improvement."
"In the next release, I would like to see fewer timeout errors."
"The support team’s response time must be improved."
"The product’s pricing needs improvement."
"It would be a much better tool if it could be made compatible with other cloud services as well since this is an area the product currently lacks."
"I would like to have an integrated dashboard on top of it and a better UX to look at. The dashboard could be better in terms of integration with other tools. We should be able to have a single pane of glass across all the tools that we use where Jenkins is the pipeline. This can be a very good upgrade to it."
"Support should be provided at no cost, as there is no free support available for any of the free versions."
"There is no way for the cloud repositories to trigger Jenkins."
"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."
"Jenkins is not an easy solution to use and the configuration is not simple. They can improve the solution by adding a graphical interface that is more user-friendly."
"I would like them to provide space for people to have a central node that stores all the logs of workspace information in a distributed fashion to facilitate backup and restoration. Currently, everything is stored on one node, so you need to set up distributed storage or an endpoint that you can use for backing up your information."
"It does not have a very user-friendly interface."
"The enterprise version is less stable than the open-source version."
AWS CodePipeline is ranked 3rd in Build Automation with 13 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, GitHub Actions, Tekton and Bamboo, whereas Jenkins is most compared with GitLab, Bamboo, IBM Rational Build Forge, Harness and Tekton. 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.