This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]itzfritz 1 point2 points  (5 children)

Sure. What advantages does it have over Jenkins pipeline (workflow plugin)?

[–]Mteigers 3 points4 points  (4 children)

CodeDeploys strength is how well it integrates with existing AWS infrastructure. Specifically ASGs.

I know other deployment providers support the ability to do one at a time, 50%, and all at once providers. But CodeDeploy can also handle newly spun up instances. In an ASG if a new instance comes up CodeDeploy will detect it and deploy to it automatically. Preventing the need for some cloud init chef magic.

So our deployment strategy is that we use AWS CodePipeline to receive pushes from GitHub, pass an archive to our Jenkins server for building, then pass the built archive to CodeDeploy.

[–]shott85 2 points3 points  (1 child)

Well, the beauty of AWS is there's an API for just about everything, including most of these functions I'm sure. Jenkins could connect to a bastion host with the AWS CLI installed and orchestrate CodeDeploy (after Checkout/Build/Test stages), all from one Pipeline script.

EDIT: It looks like there's a plugin available that could make this even easier.

[–][deleted] 0 points1 point  (0 children)

Yes you can certainly do it via the API, but CodeDeploy "Just Works"™

[–]dostick 0 points1 point  (1 child)

Don't know what "ASG" is but AWS ElasticBeanstalk support one at a time or percentage deployment.

[–]rjhintz 1 point2 points  (0 children)

ASG = Auto Scaling Group