Answers: <p>Maybe cost is a factor? And it's open-source? I would think those two factors alone make it popular amongst startups.</p>
  
  <p>I work in an enterprise environment and we use AWS a lot but still use Jenkins as our main build tool.</p>
  
  <p>Sure there are better, more polished options, but like I said... cost and open-source, and also many people are used to it already.</p>
  
Answers: CC BY-SA 4.0
Answers: 2019-05-23T19:35:27.460Z
Answers: 2019-05-23T19:35:27.460Z
Answers: System Five
Answers: <p>Jenkins has been around for longer so it has a larger installed base.  It doesn't matter if AWS has something that is cheaper and better.  Many places don't want to put the time and energy into upgrading Jenkins.  Migrating to a new CI pipeline is even "scarier" -- regardless of whether it would be a wise strategic decision.</p>
  
  <p>Jenkins 1.x made this far worse because of needing extensions for basic functionality.  Different departments wanting different plugins that wouldn't play well together led to multiple Jenkins instances.  Even if the technical challenge of merging these were relatively minor, the chance of getting departments that could never agree on anything before to suddenly decide that they can migrate to some new thing -- that is missing some feature from a plugin they can't live without -- seems pretty slim.</p>
  
Answers: CC BY-SA 4.0
Answers: 2019-05-26T01:20:04.113Z
Answers: 2019-05-26T01:20:04.113Z
Answers: chicks
Body: <p>I have searched few job sites. Many companies are searching engineers who can handle Jenkins as CI platform.
  I think the Aws CodePipeline is easier than Jenkins.</p>
  <p>Anyone can advise me, please.
  Thank you in advance.</p>
  
Comments: CC BY-SA 4.0
Comments: 2019-05-28T20:46:15.710Z
Comments: Why tie yourself and all of your development to one particular cloud provider?
Comments: casey vega
Comments: CC BY-SA 4.0
Comments: 2019-06-05T20:51:51.517Z
Comments: @caseyvega of course I can go for Jenkins. My question pointed that I’m just curious the reason most of them are prepare it than AWS CodePipeline.
Comments: Chachatonel Hashimotto
Tags: <jenkins><jenkins-pipeline><aws-codepipeline>
Title: Why many companies prefer Jenkins than Aws CodePipeline?
UserDisplayName: Chachatonel Hashimotto
ThreadText: # Why many companies prefer Jenkins than Aws CodePipeline?
  
  (Asked by: username_0 on 2019-05-23)
  
  I have searched few job sites. Many companies are searching engineers who can handle Jenkins as CI platform.
  I think the Aws CodePipeline is easier than Jenkins.
  
  Anyone can advise me, please.
  Thank you in advance.
  
  **Tags:** jenkins, jenkins-pipeline, aws-codepipeline
  
  > **Comments:**
  > **username_1**: Why tie yourself and all of your development to one particular cloud provider?  
  > **username_0**: @username_1 of course I can go for Jenkins. My question pointed that I’m just curious the reason most of them are prepare it than AWS CodePipeline.  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_3 on 2019-05-26. Score: 4 | Accepted answer
  
  Jenkins has been around for longer so it has a larger installed base. It doesn't matter if AWS has something that is cheaper and better. Many places don't want to put the time and energy into upgrading Jenkins. Migrating to a new CI pipeline is even "scarier" -- regardless of whether it would be a wise strategic decision.
  
  Jenkins 1.x made this far worse because of needing extensions for basic functionality. Different departments wanting different plugins that wouldn't play well together led to multiple Jenkins instances. Even if the technical challenge of merging these were relatively minor, the chance of getting departments that could never agree on anything before to suddenly decide that they can migrate to some new thing -- that is missing some feature from a plugin they can't live without -- seems pretty slim.
  
  
  ---
  
  ### Answer by username_2 on 2019-05-23. Score: 1
  
  Maybe cost is a factor? And it's open-source? I would think those two factors alone make it popular amongst startups.
  
  I work in an enterprise environment and we use AWS a lot but still use Jenkins as our main build tool.
  
  Sure there are better, more polished options, but like I said... cost and open-source, and also many people are used to it already.
  
  
  ---
  
  