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 with other AWS services has streamlined our workflow."
"The integration is a good feature."
"The integration is a good feature."
"It works seamlessly with AWS Elastic Container Registry (ECR)."
"The solution provides good integrations."
"It is open source, flexible, scalable, and easy to use. It is easy to maintain for the administrator. It is a continuous integration tool, and its enterprise version is quite mature. It has good integrations and plug-ins. Azure DevOps can also be integrated with Jenkins."
"Has a good interface, is reliable and saves time."
"I like the business logs. It's a very useful tool. Client-server communication is also very fast."
"It's very useful when you want to automate different processes from beginning to end."
"We significantly reduced build times of large projects (more than 80k lines of Scala code) using build time on Jenkins as a time sample. It reduced the developer write-test-commit cycle time, and increased productivity."
"It's very easy to learn."
"Jenkins's open-based framework is very valuable."
"It is very useful for us to be able to collect and manage automatic processing pipelines."
"While working on building images for multiple applications within a single script, I encountered an issue where looping functionality was not supported as expected."
"They can further improve the integration of the Bitbucket for CodeBuild."
"The deployment fails sometimes."
"There is no persistent storage or preservation of workspace between the builds."
"Centralized user management would be helpful."
"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."
"The support for the latest Java Runtime Environment should be improved."
"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."
"This solution would be improved with the inclusion of an Artifactory (Universal artifact repository manager)."
"We would like to see the addition of mobile simulators support to this solution, as part of its open-source offering. We currently have to carry out manual testing for these platforms."
"They need to improve their documentation."
"The solution could improve by having more advanced integrations."
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, GitHub Actions, CircleCI and Tekton, whereas Jenkins is most compared with GitLab, Bamboo, AWS CodePipeline, IBM Rational Build Forge and Chef. 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.