AWS CodeBuild vs Jenkins comparison

"The most important thing is that it's self-contained in an AWS account, and it's all linked to the customer's AWS account."

"The solution provides good integrations."

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

"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 integration is a good feature."

"It works seamlessly with AWS Elastic Container Registry (ECR)."

"The deployment of traditional Jenkins is easy."

"I like the business logs. It's a very useful tool. Client-server communication is also very fast."

"A lot of support material exists via a single web search of exactly what you're looking for."

"It is very useful for us to be able to collect and manage automatic processing pipelines."

"Jenkins is very user-friendly."

"GitHub linking is pretty good. We have a deployment application where we can run our tests and add various variables to be passed as assertions to those tests. This is pretty fluid with 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."

"Jenkins has a lot of built-in packages and tools."

"There have been times when CodeBuild has shown some instability, like bugs or breakdowns."

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

"The front-end interface and the management are somewhat challenging, and there's a lot of space for improvement."

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

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

"The documentation on plugin development could be better: more examples. ​"

"I sometimes face a bottleneck when installing the plugins on an offline machine. Mapping the dependencies and then installing the correct sequence of dependencies is a nightmare, and it took me two days to do it."

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

"Upgrading and maintaining plugins can be painful, as sometimes upgrading a plugin can break functionality of another plugin that a job is dependent on."

"We need more licensed product integrations."

"It would be helpful if they had a bit more interactive UI."

"The learning curve is quite steep at the moment."

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

"We pay a monthly licensing fee."

"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, so it is free."

"This is an open-source solution for the basic features. However, if an organization wishes to include specific functionality, outside of the basic package, there are extra costs involved."

"There is no cost. It is open source."

"Jenkins is an open-source platform."

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

"The open-source version is free, but small companies would not be able to afford the cloud-based version."

"It is an open source."

"The tool is open-source."