Closed LordA98 closed 3 years ago
This specific issue was being caused because the server was running out memory so the Node process for the deployment was being cancelled and hence the build was failing.
I had initially been using a 1 CPU / 1GB RAM Ubuntu 20.04 server on Linode ($5). I increased this to 1 CPU / 2GB RAM ($10) but still had the same error.
Increasing it again to 2 CPU / 4GB RAM ($20) resolved the issue and the deployment succeeded. However, the job still took 45 minutes to run. The second and third runs took ~20 minutes on the same server.
Having to use a $20 server for a CICD deployment seems a bit excessive so I will try to improve it and bring this down to the $10 server.
I will close this issue as I found the solution for this specific problem but would appreciate any suggestions for performance improvements.
I'm trying to setup a GitLab Runner for my CICD pipeline. The runner is installed on a server running Ubuntu 20.04.
I have installed all of the necessary packages directly to the machine (Meteor, Node, NPM, yarn, mup, etc). Meteor and Mup are also installed in the script in the GitLab YAML file. If I can get this working directly on the Ubuntu machine, I would assume I can just copy the fixes to the GitLab YAML.
I'm not getting much output from
mup deploy
, so I am struggling to debug it.Mup version (
mup --version
):1.5.3
Meteor version:
1.11.1
Node version:
12.22.1
(A docker image for node:12.18.4 is used in the GitLab YAML at the moment)Mup config
Output of command (DEBUG=mup* mup deploy --verbose)
Building for web.browser.legacy
is not always the same. Sometimes it fails on other sections (Minifying app code, etc).I've been struggling with this for a few days. I'm finding it hard to find the cause of this issue.
I develop the application locally on a MacOS system. I can deploy perfectly fine from this but I am struggling to deploy directly from the Ubuntu machine or from Docker (locally and on the VM).