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 integration with other AWS services has streamlined our workflow."
"The integration is a good feature."
"The solution provides good integrations."
"The most valuable feature of Jenkins is its continuous deployment. We can deploy to multi-cluster and multi-regions in the cloud."
"The most valuable features of Jenkins are creating builds, and connecting them with Sonar for Sonar analysis. Additionally, we connect it with other vulnerability tools, such as WhiteSource which is useful."
"Jenkins' most valuable feature is Pipeline."
"This is a great integration tool and very powerful."
"Having builds and test tasks triggered on commit helps not to break the product."
"We have started to integrate Pipelines as a part of a build, and built a library of common functions. It simplified and made our build scripts more readable."
"Jenkins can be used for elastic management, if you have any sensitive data or credentials you can use them across the environment. Additionally, the solution is easy to use and can be used across multiple use cases."
"Jenkins is a very mature product."
"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 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."
"I think an integrated help button, that respected the context of the change/work in hand, would be a worthwhile improvement."
"The user interface could be updated a little."
"The enterprise version is less stable than the open-source version."
"Jenkins takes a long time to create archive files."
"It can be improved by including automated mobile reporting integrations."
"There are some difficulties when we need to execute the DB script."
"Centralized user management would be helpful."
"Improvement-wise, I would want the solution's user interface to be changed for the better. In short, the solution can be made more user-friendly."
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.