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 solution provides good integrations."
"It works seamlessly with AWS Elastic Container Registry (ECR)."
"The integration is a good feature."
"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."
"The solution is scalable and has a large number of plugins that can help you scale it to your needs."
"It's very easy to learn."
"This solution has helped us in automating the build and test process, reducing time."
"I like that you can find a wide range of plugins for Jenkins."
"When we have manual tasks, we have to depend on multiple technical teams. With Jenkins, we can bring all the technologies together by the click of a button. We can see results without having to depend on different teams. Jenkins makes life easy for the database and DevOps teams."
"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."
"It can scale easily."
"The deployment fails sometimes."
"There is no persistent storage or preservation of workspace between the builds."
"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."
"This solution could be improved by removing the storage of unnecessary data such as the history of test deployments that were unsuccessful."
"Jenkins could improve by allowing more scripting languages. We need to use Groovy scripting and it is difficult to debug and it is not ideal for creating file scripts. We tried to search for assistance but we did not find much help."
"It would be helpful if they had a bit more interactive UI."
"Partition security for the workflow of projects is not yet an option."
"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 disadvantage of Jenkins is writing Groovy scripts. There are other CI tools where you do not need to write this many scripts to manage and deploy."
"Centralized user management would be helpful."
"Its schedule builds need improvement. It should have scheduling features in the platform rather than using external plug-ins."
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.