AWS CodeDeploy vs. License4J Floating License Server

For greenfield projects built on AWS there are very few reasons why not to choose AWS CodeDeploy. It works out of the box and integrates seamlessly into your cloud environment. If you plan to migrate your existing legacy builds away e.g. from Jenkins, you may need to reserve a substantial amount of time for that and the benefits gained may not be worth the effort.

Incentivized

• Automate to deploy to AWS cloud environments
• Maximize application availability during product deployment
• AWS CodeDeploy provides CLI or web management console which can be viewed or edited at any environment

Incentivized

• When deploying a branch, sometimes the repository won't auto-populate, and you have to add the source manually

Incentivized

Jenkins supports a lot of plugings. Also with Jenkins, it is possible to manage everything through our own server. Those are 2 points where I rate Jenkins as one of the best DevOps Tool

Incentivized

• 1-2 months per year of working time was saved from administration compared to on-prem legacy solution.
• Teams can trust more on the CI/CD pipeline and the deployments are faster, so the teams can deploy 10-15% more often compared to on-prem legacy solutions.
• Developers tend to desire more bells and whistles than CodeDeploy can offer, there has been some critique but this can be seen also as "editor war" (everyone has their opinion).

Incentivized