Generator-jhipster: flaky cpu/memory overflow issues when building jar for production in gitlab

[geyuqiu]

build jar fails sometimes on a gitlab server with 1.78G RAM

Overview of the issue

Motivation for or Use Case

Reproduce the error

Related issues

Suggest a Fix

JHipster Version(s)

JHipster configuration

Entity configuration(s) entityName.json files generated in the .jhipster directory

Browsers and Operating System

• [x] Checking this box is mandatory (this is just to show you read everything)

[geyuqiu]

during
node --max_old_space_size=4096 node_modules/webpack/bin/webpack.js "--config" "webpack/webpack.prod.js" "--profile"

[SudharakaP]

@geyuqiu : Could you please fill in the issue template fully so that others can reproduce your issue more easily. 😄

[pascalgrimaud]

Simply increase the memory on your GitLab server ?

[geyuqiu]

trying with 1024 instead of 4096 (4GB) https://medium.com/@vuongtran/how-to-solve-process-out-of-memory-in-node-js-5f0de8f8464c, https://stackoverflow.com/questions/48387040/nodejs-recommended-max-old-space-size/48392705

[geyuqiu]

Simply increase the memory on your GitLab server ?

if it is so easy :)

[PierreBesson]

I would recommend at least 4Gb of ram for the webpack build. For Gitlab, I recommend setting up an external Gitlab runner : https://docs.gitlab.com/runner/install/

[geyuqiu]

@PierreBesson I will have this in mind for next cloud project :)