Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

AWS CodeBuild – Build and test code with continuous scaling

aws.amazon.com

Post reply on HN
Print view View original

31–40 of 46 posts

Re: AWS CodeBuild – Build and test code with continuous scaling

#31

Post by timoth »

luhn wrote: post #19

I'm excited about what this means for Lambda. Building Lambda packages has always been a pain because much of the time it needs to be built on Amazon Linux to work, meaning most (all?) CI SaaS solutions are out the window. I assume CodeBuild will run Amazon Linux and CodePipeline integrates with Lambda, so this should make setting up continuous deployment with Lambda much easier.

AWS now provides a container image for Amazon Linux which might also be an option, depending on the CI SaaS: https://aws.amazon.com/blogs/aws/new-amazon-linux-container-...

Re: AWS CodeBuild – Build and test code with continuous scaling

#32

Post by mesozoic »

FAQ says this. Is there any examples on setting it up? It isn't obvious from inside CodePipeline.

Yes. The CodePipeline Plugin for Jenkins can be used to integrate CodeBuild into Jenkins jobs. The build jobs are sent to CodeBuild, eliminating the need for provisioning and managing the Jenkins worker nodes.

Re: AWS CodeBuild – Build and test code with continuous scaling

#34

Post by STRML »

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

Re: AWS CodeBuild – Build and test code with continuous scaling

#35

Post by St-Clock »

St-Clock wrote: post #9

I'm trying to find if they offer or plan to offer these features: 1. Caching. CircleCI and Travis cache intermediate build artifacts (e.g., virtualenv in python) to reduce build time. 2. Github pull request integration (red cross on pull requests if the build fails). 3. Chat integration. Sending a message to slack or hipchat when the build fails. 4. SSH into build container. Very handy for rare but difficult to local…

So after perusing the documentation, it seems that:

1. No cache. You need to build your own.

2. No obvious github integration. You can pull code from github but that's it.

3. Notifications are managed with SNS. So you need to use lambda or something like that for Slack Notifications.

4. No obvious ssh support. Would need to check the dockers image they use to be 100% sure.

Re: AWS CodeBuild – Build and test code with continuous scaling

#36

Post by Malkav »

Gave it a try, seems to be kinda slow building docker images. An image that take 2 minutes in my machine is taking around 10 minutes in CodeBuild. The build seems to freeze a little between docker build steps :

--- Example 1 ---

[Container] 2016/12/01 22:39:59 Step 9 : EXPOSE 3000

[Container] 2016/12/01 22:40:31 ---> Running in 1c6e3a4dbec8

[Container] 2016/12/01 22:40:45 ---> 602aa4bc97ac

-----------------

--- Example 2 ---

[Container] 2016/12/01 22:36:00 Step 4 : WORKDIR /src

[Container] 2016/12/01 22:36:32 ---> Running in 98800352e6c2

[Container] 2016/12/01 22:36:45 ---> b437afe2a1c5

-----------------

Not sure if this caused by the fact its a docker inside docker implementation.

Re: AWS CodeBuild – Build and test code with continuous scaling

#37

Post by venantius »

debaserab2 wrote: post #27

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.

This was my thought as well. I've seen them offer a few different of these "workflow engines" that seemed to be quite clearly oriented towards build services, although this is the first that's very explicitly focused on that.

Re: AWS CodeBuild – Build and test code with continuous scaling

#38

Post by vacri »

debaserab2 wrote: post #27

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' kind of thing (less flexibility and control)
    Beanstalk: a simpler version of OpsWorks? (never tried it)
    CodeDeploy: install an agent, it pulls code/artifacts (janky workflow)
    CodeBuild: no idea, just been released
    Just Using The Web Console: convenient, but manual process (labour-intensive, prone to manual errors)
On the CI thing - from my experience at one of the places I work, there are a thousand CI systems out there, but very few CD systems. Pretty much anything can schedule and track builds, but few things schedule and track deploys (which gets suprisingly tricky suprisingly quickly). CD is the 'last mile'...

EDIT: missed some that I've never looked at. It is getting crazy...

    CodeCommit: looks like it might be a 'github'?
    CodePipeline: No idea. Perhaps a spruced-up version of CodeDeploy?

Re: AWS CodeBuild – Build and test code with continuous scaling

#39

Post by gsharma »

STRML wrote: post #34

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

> 4. We need a way to execute actions on failure.

I am curious to know what kind of actions would they be other than notifying via chat/email?

Re: AWS CodeBuild – Build and test code with continuous scaling

#40

Post by TomFrost »

gsharma wrote: post #39
STRML wrote: post #34

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

> 4. We need a way to execute actions on failure. I am curious to know what kind of actions would they be other than notifying via chat/email?

For one, hitting the Github API to put failed build markers against commits and PRs. CodeBuild doesn't appear to have the same Github integration that most other CIs do out of the box.
Post reply on HN