5 ms·
AWS codepipeline/codebuild still takes a really long time. think 1 minute to notice a commit, 2 minutes to download code, 3-8 minutes to get a codebuild runner,
by pluto_modadic 2y ago
AWS codepipeline/codebuild still takes a really long time. think 1 minute to notice a commit, 2 minutes to download code, 3-8 minutes to get a codebuild runner, however long your build is, and 30 seconds to update the lambda.
Especially when you don't have a good local AWS runner, vs using a HTTP service you can run and live reload on your laptop.
deploying to prod in less than 10 seconds, or even /live reloading/ the AWS service would be awesome.
- abadpoli 2y agoFor fast iteration, our developers build, test and deploy locally using cdk deploy directly into their dev account, no need to wait around for the pipeline to do all those steps. Then when they’re ready, higher environments go through the pipeline. CDK has a new(ish) feature called hotswap that also bypasses CloudFormation and makes deploys faster.
- chuckadams 2y agoThe equivalent of hotswap in SAM would be `sam sync --code --watch`. Works in seconds, though I still prefer to test locally as much as possible.
- deleted 2y ago[deleted]