How many different CI workflow tools are on AWS these days? How do I know which one to pick? I really wish Amazon would spend some time building comparison guides for their services. Each one feels very silo'd off from each other and the crossover in functionality seems very high.
Cloudformation is for when you have a team of ops or a workflow where you have a lot of repeated resource recreation; Beanstalk is for when you have no ops, and you're happy for someone else to handle the environment; CodeDeploy is just yuck; and don't know about this one yet. Cloudformation: infrastructure-as-code (but has sharp edges) (doesn't touch your app/code directly) Opsworks: wizard-style 'drop your app here…
AWS CodeBuild – Build and test code with continuous scaling
41–46 of 46 posts
Re: AWS CodeBuild – Build and test code with continuous scaling
#42How many different CI workflow tools are on AWS these days? How do I know which one to pick? I really wish Amazon would spend some time building comparison guides for their services. Each one feels very silo'd off from each other and the crossover in functionality seems very high.
Cloudformation is for when you have a team of ops or a workflow where you have a lot of repeated resource recreation; Beanstalk is for when you have no ops, and you're happy for someone else to handle the environment; CodeDeploy is just yuck; and don't know about this one yet. Cloudformation: infrastructure-as-code (but has sharp edges) (doesn't touch your app/code directly) Opsworks: wizard-style 'drop your app here…
I recently inherited an app that uses OpsWorks. The deploy process is actually really nice, but I notice that it doesn't receive a lot of updates from AWS. Since OpsWorks came out when Chef was hot, and now Chef seems to be less popular than Ansible and/or docker. I wonder what the future holds for me if Chef continues to decline in popularity.
Re: AWS CodeBuild – Build and test code with continuous scaling
#43Seems pretty nice. A few things I'd like to see: 1. We should be able to configure this for a few/all branches (including PRs) and have conditional build tasks based on branch. 2. We need be able to access resources inside a VPC. 3. Turnkey chat integrations would be nice, but it's not a big deal to just curl. 4. We need a way to execute actions on failure.
CodePipeline has codebuild and lambda integrations, you could use the lambda functions to do what you want after success/failure.
Re: AWS CodeBuild – Build and test code with continuous scaling
#44Seems pretty nice. A few things I'd like to see: 1. We should be able to configure this for a few/all branches (including PRs) and have conditional build tasks based on branch. 2. We need be able to access resources inside a VPC. 3. Turnkey chat integrations would be nice, but it's not a big deal to just curl. 4. We need a way to execute actions on failure.
From my initial testing, this looks like an annoying "no". There doesn't appear to be any way to set the VPC or security group in which the build executes, only an IAM role.
(which already makes it a non-starter for my use case with a private npm-enterprise server)
Re: AWS CodeBuild – Build and test code with continuous scaling
#45I wrote up how we plan to use this in the Convox platform here: https://convox.com/blog/codebuild/
Practically speaking, we're working through PCI compliance. Getting builds off of production services and root-enabled docker daemons is a huge win.
Re: AWS CodeBuild – Build and test code with continuous scaling
#46Still no way to build iOS applications.