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."The integration is a good feature."
"The integration is a good feature."
"The solution provides good integrations."
"It works seamlessly with AWS Elastic Container Registry (ECR)."
"The integration with other AWS services has streamlined our workflow."
"We really appreciate that this solution is plug and play. When coding in the version control system, this product completes the build process automatically."
"Continuous Integration. Jenkins can integrate with almost any systems used for application development and testing, with its plugins."
"The most valuable feature is its ability to connect with different tools and technologies."
"Distributed execution of build and test jobs."
"For business needs, Jenkins is the most relevant choice because it can be self-hosted, the price is good, it’s robust, and requires almost no effort for maintenance."
"Jenkins is very stable."
"Jenkins is stable, user-friendly, and helps with continuous integration. As of today, I can't see any tool that's better than Jenkins."
"Jenkins's open-based framework is very valuable."
"There is no persistent storage or preservation of workspace between the builds."
"The deployment fails sometimes."
"They can further improve the integration of the Bitbucket for CodeBuild."
"While working on building images for multiple applications within a single script, I encountered an issue where looping functionality was not supported as expected."
"The learning curve is quite steep at the moment."
"Centralized user management would be helpful."
"It can be improved by including automated mobile reporting integrations."
"Support should be provided at no cost, as there is no free support available for any of the free versions."
"The product should provide more visualization as to how many pipelines are performing and how many builds are happening. It should also integrate with Kubernetes and OpenShift."
"There is no way for the cloud repositories to trigger Jenkins."
"Tasks such as deployment, cloning, database switchover, and all other database missions and tasks are being done through Jenkins. If a job does not go through, at times the error message does not clearly indicate what caused the failure. I have to escalate it to the Jenkins DevOps team just to see what caused the failure. If the error message is clear, then I wouldn't have to escalate the issue to different teams."
"Sometimes you have Jenkins restarting because of OOM errors."
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.
