-
Notifications
You must be signed in to change notification settings - Fork 38
Long time to deploy the pipeline #60
Comments
@s1mrankaur Is that for the entire pipeline or just the deploy stage? You can try and assign more CPU/Memory to the CodeBuild job: https://docs.aws.amazon.com/codebuild/latest/userguide/build-env-ref-compute-types.html |
@srijitm Deploy stage: The command I am running is:
|
Remove the --all and include only the stack you want to deploy. |
@srijitm Is there a way for it to automatically detect what stack should be deployed? |
No. Cloudformation (and therefore CDK) only pushes the changes anyways. However, it may take some time for it to do the diff. |
That explains it. Thank you |
Also, I have a question related to issue #61 . Does npm install command need to be run in all the scripts i.e build.sh, deploy.sh and test.sh ? lerna run commands seem to be running okay in build.sh where the npm install command runs but throws MODULE_NOT_FOUND errr in deploy.sh and test.sh @srijitm |
You should take a look and see if everything is being packaged correctly (can probably run the |
@srijitm lerna created symlinks but I tried adding npm install in each of the 3 shell scripts i.e test.sh, build.sh and deploy.sh but still am getting the error in test.sh and deploy.sh I did run but it still failed. while the same command runs just fine in build.sh So here's what my build.sh looks like:
Here's what my test.sh looks like:
The build stage completed okay, and the test stage throws this error:
|
@srijitm If it's relevant, I needed the pipeline to use node runtime 15, so I had added following in 1.tets-project.js
and removed:
|
It takes a fairly long time (About 6-8 minutes( to deploy on making a change of 1 line of code as well. Is there a way around it?
The text was updated successfully, but these errors were encountered: