AWS CodeBuild vs Jenkins comparison

"The tool is used to build and test code. I find its biggest advantages are elasticity and reliability. We can easily assign as many computing resources as needed to build our code, which is much simpler than traditional methods that require server upgrades. It's a serverless tool, so it's very flexible and elastic."

"A valuable feature is the support for third-party repositories such as Bitbucket, GitLab, or GitHub."

"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."

"The integration with other AWS services has streamlined our workflow."

"The initial setup is pretty simple."

"I am not aware of the available options in the market right now compared to Jenkins, but I am pretty much happy with the service that Jenkins is providing our company."

"The most valuable features of Jenkins are the integration with GitHub, and the automation for deployment."

"This solution has helped us in automating the build and test process, reducing time."

"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."

"We can schedule anything with Jenkins, which is useful for deployment or anything that requires scheduling. It also has multiple plugins we can use for Maven, JUnit, etc."

"The deployment of traditional Jenkins is easy."

"Jenkins is a very mature product."

"The deployment fails sometimes."

"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."

"For improvement, I'd suggest more build instance-type options. There's a big jump from 15 gigabytes of RAM to 150, and I'd like something in between as the larger option is too expensive for our needs."

"They can further improve the integration of the Bitbucket for CodeBuild."

"Notifications could be added, or SNS integration could be included so that notifications can be received on every build, whether the build fails or succeeds."

"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."

"Jenkins relies on the old version of interface for configuration management. This needs improvement."

"I think an integrated help button, that respected the context of the change/work in hand, would be a worthwhile improvement."

"Integrating Jenkins with other tools or solutions has presented some challenges. For instance, when attempting to integrate Jenkins with Kubernetes, I encountered numerous errors, which took several days to resolve. In Jenkins, adding a feature typically involves incorporating the repository feature separately. Jenkins lacks built-in Git repository functionality, necessitating an external Git repository to store Jenkins manifests."

"Jenkins could improve in areas related to Kubernetes and Docker container integration, like machine allocation of nodes and Marshaling integration improvements."

"The solution's UI can use a facelift and the logs can use more detailed information."

"There are a lot of things that they can try to improvise. They can reduce a lot of configurations. It is currently supporting Groovy for scripting. It would be really good if it can be improvised for Python because, for most of the automation, we have Python as a script. It would be good if can also support Python. We have a lot of Android builds. These Android builds can be a part of Jenkins. It can have some plug-ins or configurations for Android builds. There should also be some internal matrix to check the performance. We also want to have more REST API support, which is currently not much in Jenkins. We are not able to get more information about running Jenkins. More REST API support should be provided."

"Support should be provided at no cost, as there is no free support available for any of the free versions."

"We pay a monthly licensing fee."

"Despite the cost, it is worth the investment."

"AWS CodeBuild is free. We only pay for our code's compute resources during the build process. For example, if our code takes ten minutes to build, we only pay for those ten minutes of computing time. CodeDeploy and CodePipeline are free because they're serverless and don't require computing resources. CodeCommit has minimal costs for storing code."

"Jenkins is open source and free."

"Jenkins is a free open-source server."

"Some of the add-ons are too expensive."

"We are using the freeware version of Jenkins."

"The solution is open source."

"The pricing for Jenkins is free."

"It is an open source."

"It is a cheap solution."