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."
"I like that you can find a wide range of plugins for Jenkins."
"Very easy to understand for newcomers."
"The most valuable features of Jenkins are the integration of automatic scripts for testing and the user's ability to use any script."
"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."
"The solution is scalable and has a large number of plugins that can help you scale it to your needs."
"Having builds and test tasks triggered on commit helps not to break the product."
"There are a large number of plugins available for integration with third party systems."
"The simplicity of Jenkins and the evolving ecosystem of Jenkins are most valuable. Today, you do not have to write a pipeline from scratch. The library functionality of Jenkins helps you to bring all those in ready-made, and you also get the best practices for them. That is a great feature of Jenkins, and that is why it is being used significantly."
"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."
"There is no persistent storage or preservation of workspace between the builds."
"The deployment fails sometimes."
"The onboarding of Jenkins should be smoother, and it should have more pipelines available as it's deployed on many different servers."
"The enterprise version is less stable than the open-source version."
"I would like to see even more integrations included in the next release."
"Support should be provided at no cost, as there is no free support available for any of the free versions."
"The solution could improve by having more advanced integrations."
"Logging could be improved to offer a clearer view."
"Sometimes, random errors of metadata are not there, which causes delays. These are essentially gaps in the information being passed to the job."
"The upgrades need improvement."
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.
