We performed a comparison between AWS CodeBuild 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."It works seamlessly with AWS Elastic Container Registry (ECR)."
"The integration is a good feature."
"The solution provides good integrations."
"The integration is a good feature."
"The integration with other AWS services has streamlined our workflow."
"Has a good interface, is reliable and saves time."
"It is very useful for us to be able to collect and manage automatic processing pipelines."
"It is a stable solution."
"Jenkins' most valuable feature is Pipeline."
"Jenkins is very user-friendly."
"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."
"This solution has helped us in automating the build and test process, reducing time."
"Having builds and test tasks triggered on commit helps not to break the product."
"The deployment fails sometimes."
"They can further improve the integration of the Bitbucket for CodeBuild."
"There is no persistent storage or preservation of workspace between the builds."
"While working on building images for multiple applications within a single script, I encountered an issue where looping functionality was not supported as expected."
"Jenkins can be improved, but it's difficult for me to explain. The initial setup could be more straightforward. If you connect Jenkins with bookings and lockouts, it can be challenging."
"The documentation could be more friendly, and more examples of how to use it."
"The solution's UI can use a facelift and the logs can use more detailed information."
"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."
"Jenkins is an open-source solution, and people tend to stay on the same version for a long time. When you look for an answer on Google, you often find something that doesn't relate to your implementation. The plugins are both the aspect of Jenkins and also one of the worst because the plugins can have different versions, so it's hard to figure out how to solve the problems."
"Jenkins should adopt the Pipeline as Code approach by building a deployment pipeline using the Jenkins file."
"And I don't care too much for the Jenkins user interface. It's not that user-friendly compared to other solutions available right now. It's not a great user experience. You can do just fine if you are a techie, but it would take a novice some time to learn it and get things done."
"There is no way for the cloud repositories to trigger Jenkins."
AWS CodeBuild is ranked 9th in Build Automation with 4 reviews while Jenkins is ranked 2nd in Build Automation with 83 reviews. AWS CodeBuild is rated 8.8, while Jenkins is rated 8.0. The top reviewer of AWS CodeBuild writes "Provides good integrations, is flexible, and has a comparable price". 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 CodeBuild is most compared with GitLab, CircleCI, GitHub Actions, Tekton and AWS CodePipeline, whereas Jenkins is most compared with GitLab, Bamboo, AWS CodePipeline, IBM Rational Build Forge and JFrog Pipeline. See our AWS CodeBuild 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.
