1 回答
- 最新
- 投票最多
- 评论最多
1
Try giving your CodeBuild instance a higher compute type since the error mentions that it's run out of memory. Also check and rule out if you are exceeding the default timeout values for the build job (1 hour). Both these options are available as Additional Configuration in Environment section.
已回答 2 年前
相关内容
- AWS 官方已更新 1 年前
- AWS 官方已更新 1 年前
- AWS 官方已更新 3 年前
I was able to resolve this issue by increasing the default configuration in codebuild from smaller cpu to larger one. it was indeed a memory issue.
Another question, what triggers this memory issue, how to ensure that this memory issue doesn't occur frequently and I don't need to increase the memory frequently.
I'm no expert with npm run build. But unless the originally reported issue was intermittent, I would assume that the codebuild instance was undersized. Now that you changed the instance, the issue should not recur soon. The only time you might need more memory / cpu is when whatever npm build does in the background needs more processing capacity due to increased dependencies or more things to build... something of that sort...