Run all builds in GitHub Actions? about aws-lambda-layers HOT 4 CLOSED

I did test AWS CodeBuild public builds, so logs would be public as well. However, I completely take your point that GH Actions has a much better UX/DX than CodeBuild. Personally, I get by easily with both of them since I have nearly 6 years experience with CodeBuild. At this point I'd say the advantage of CodeBuild is that we have nearly everything done to use it ready to go and AWS offers much bigger instance size (better parallel processing) while with GH Actions we would need to learn how to setup OIDC and vCPU is much smaller / only 2 threads would be possible instead of 7, IIRC.

from aws-lambda-layers.

Thanks for the quick response! I'm tempted to look into https://github.com/aws-actions/aws-codebuild-run-build

I forgot that CodeBuild logs could be public, but the UI… is really offputting and confusing. Having a single entrypoint and model for contributors would be great. Maybe the link above will help, I'll check this out.

from aws-lambda-layers.

Just gave this a try: I was able to set up the same kind of role except using OIDC, and the publication of layers only took 7 minutes. That's awesome!

I'll try to go all the way (missing the publication of Docker images) but so far this is working out really good with GitHub only. Building ARM images also wasn't an issue (not slow).

from aws-lambda-layers.

It's working really great so far, I'll stick with it. I'm also able to trigger layer updates once this build is done (https://github.com/brefphp/aws-lambda-layers/blob/main/.github/workflows/release.yml#L53-L67) which is pretty awesome!

from aws-lambda-layers.