AWS CodePipeline vs Jenkins comparison

"AWS CodePipeline offers multiple integrations and it has its own set of features in the area of code scanning and dynamic code testing."

"Another big advantage is observability."

"The product is cost-effective and integrates well with the AWS environment."

"The integrations are good."

"AWS CodePipeline's most valuable feature is its seamless integration with other AWS services, making it easier to orchestrate deployment processes."

"The tool's recent version helps us to run pipelines in parallel. The integration with other AWS services has greatly impacted our use of AWS CodePipeline. It made tasks such as integrating with Jira and provisioning instances much easier."

"The management of CodeBuild and CodeDeploy on a three-point trigger basis is an important feature."

"It's a perfect solution if you are just using AWS."

"Jenkins has been instrumental in automating our build and deployment processes."

"The initial setup is simple."

"The most valuable features of Jenkins are its ease of use and good plugins available. You are able to connect to a lot of solutions."

"Jenkins is very stable."

"The most valuable aspect of Jenkins is pipeline customization. Jenkins provides a declarative pipeline as well as a scripted pipeline. The scripted pipeline uses a programming language. You can customize it to your needs, so we use Jenkins because other solutions like Travis and Spinnaker don't allow much customization."

"We really appreciate that this solution is plug and play. When coding in the version control system, this product completes the build process automatically."

"It is a stable solution."

"Jenkins has built good plugins and has a good security platform."

"If you're talking about multi-cloud, you can't use it."

"The migration process from one source code to another needs improvement."

"In AWS CodePipeline, we can only use certain tools for which AWS provisions plugins."

"From my perspective, some in-built capabilities could be enhanced."

"It would be a much better tool if it could be made compatible with other cloud services as well since this is an area the product currently lacks."

"It would be best if AWS CodePipeline provided multiple integration options directly by providing some URLs."

"AWS CodePipeline is quite a simple tool mostly for management and creating automation."

"In the next release, I would like to see fewer timeout errors."

"Some kind of SaaS product would be helpful in providing organizational structure."

"Sometimes you have Jenkins restarting because of OOM errors."

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

"We sometimes face challenges during version upgrades, such as failures when migrating Kubernetes versions."

"They need to improve their documentation."

"Jenkins could improve by adding the ability to edit test automation and make time planning better because it is difficult. It should be easier to do."

"This solution would be improved with the inclusion of an Artifactory (Universal artifact repository manager)."

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

"I would rate the product's pricing a five out of ten."

"AWS offers free business or enterprise support services."

"AWS CodePipeline is quite affordable. I've been running around four pipelines and the cost is around one dollar per month. It rarely exceeds two dollars."

"Compared to other cloud services, AWS CodePipeline falls a bit more on the pricey side. I see that the price of the product has been increasing for the past few years."

"The pricing of this solution is dependent upon your needs including how many jobs you daily and how many times the developer will be changing codes and completing deployments."

"The pricing is manageable."

"The price of the product depends on how many times you run it. The tool offers a pay-as-you-go model."

"AWS charges you based on the number of pipelines you have and how active they are, and I also think that the root account user knows about all the price-related metrics."

"The pricing for Jenkins is free."

"I used the free OSS version all the time. It was enough for all my needs."

"It is an open source."

"Jenkins is open source and free."

"In our company, we do pay for the licensing of the solution."

"Jenkins is open-source, so it is free."

"​It is free.​"

"Jenkins is a free solution, it is open source."