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."
"It's a perfect solution if you are just using AWS."
"I find performance to be the most valuable CodePipeline feature. It works perfectly and smoothly."
"The integrations are good."
"The product is cost-effective and integrates well with the AWS environment."
"Code deployment is the best feature."
"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."
"AWS CodePipeline offers multiple integrations and it has its own set of features in the area of code scanning and dynamic code testing."
"The deployment of traditional Jenkins is easy."
"The solution is scalable and concurrent users have access to the platform."
"It's very useful when you want to automate different processes from beginning to end."
"The most valuable aspect of Jenkins is pipeline customization. Jenkins provides a declarative pipeline as well as a scripted pipeline. The scripted pipeline uses a programming language. You can customize it to your needs, so we use Jenkins because other solutions like Travis and Spinnaker don't allow much customization."
"It is easy to use."
"We are using the open-source version and there is a lot of plugins and features that are available and it works on agents for free. In other solutions, it will cost extra to use them with the agent."
"It's very easy to learn."
"The most valuable features of Jenkins are the ease of use and the information about how to use the features is readily available on the internet. Additionally, with the solution, I can use other reporting tools, such as Flow."
"The support team’s response time must be improved."
"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."
"The tool does not provide automated features for evidence collection."
"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 product’s pricing 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."
"In the next release, I would like to see fewer timeout errors."
"I would like to see even more integrations included in the next release."
"It does not have a very user-friendly interface."
"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."
"Sometimes, random errors of metadata are not there, which causes delays. These are essentially gaps in the information being passed to the job."
"Partition security for the workflow of projects is not yet an option."
"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."
"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 could have better cloud functionality. Currently, we are using the existing legacy model, but we are moving toward the cloud, so it would be great if they could improve in that area. In the future, I would like more cloud features and related training materials, like a video tutorial."
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, 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.
