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 solution provides good integrations."
"The integration with other AWS services has streamlined our workflow."
"The integration is a good feature."
"The integration is a good feature."
"The most valuable features are Jenkins Pipelines for ALM and full Deploy Cycle."
"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."
"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."
"We use Jenkins to automatically build Python binaries into several OS's i.e. OS X, Ubuntu, Windows 32-bit and Windows 64-bit."
"We really appreciate that this solution is plug and play. When coding in the version control system, this product completes the build process automatically."
"We used it for all continuous integration parts, like automation testing, deployment, etc."
"With Jenkins, the pipeline will take your code from any versioning system like GitHub or Bitbucket. All the security scans can happen in one go and then all the tests also get run. You can just build one container in it and deploy it."
"The solution is scalable and concurrent users have access to the platform."
"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."
"There is no persistent storage or preservation of workspace between the builds."
"Some kind of SaaS product would be helpful in providing organizational structure."
"They need to improve their documentation."
"For this solution to be a 10, it has to be a lot more stable. Maybe the public version of Jenkins is stable, but in our case it's not stable."
"Better and easy-to-use integration with Docker would be an improvement."
"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."
"I think an integrated help button, that respected the context of the change/work in hand, would be a worthwhile improvement."
"The support for the latest Java Runtime Environment should be improved."
"The user interface could be updated a little."
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.