We started seeing test failures in Remote Execution and Ansible PR testing job when trying to precompile the assets. Seems like we started crossing limits of the memory available for the job. There has been no changes in the assets for the remote execution itself for a while.

The last build without this issue I was able to find was from [Dec 21](http://ci.theforeman.org/job/foreman_ansible-pull-request/205/) and first occurrence of [Jan 2](http://ci.theforeman.org/job/foreman_ansible-pull-request/206/)

** Execute webpack:compile
/var/lib/workspace/workspace/foreman_remote_execution-pull-request/database/postgresql/label/fast/ruby/2.5/foreman/node_modules/.bin/webpack --config /var/lib/workspace/workspace/foreman_remote_execution-pull-request/database/postgresql/label/fast/ruby/2.5/foreman/config/webpack.config.js --bail
The Apipie cache is turned off. Enable it and run apipie:cache rake task to speed up API calls.

<--- Last few GCs --->

  195960 ms: Mark-sweep 1261.7 (1439.5) -> 1261.7 (1439.5) MB, 1109.4 / 0.0 ms [allocation failure] [GC in old space requested].
  197169 ms: Mark-sweep 1261.7 (1439.5) -> 1261.7 (1439.5) MB, 1209.1 / 0.0 ms [allocation failure] [GC in old space requested].
  198660 ms: Mark-sweep 1261.7 (1439.5) -> 1265.1 (1423.5) MB, 1491.0 / 0.0 ms [last resort gc].
  200234 ms: Mark-sweep 1265.1 (1423.5) -> 1268.8 (1423.5) MB, 1573.5 / 0.0 ms [last resort gc].

<--- JS stacktrace --->

==== JS stack trace =========================================

Security context: 0x12cdac3cf781 <JS Object>
    1: InnerArrayForEach(aka InnerArrayForEach) [native array.js:~935] [pc=0x2b91ba124e0f] (this=0x12cdac304381 <undefined>,bq=0x23b6a4ec2971 <JS Function (SharedFunctionInfo 0x3371ba6ffda9)>,br=0x25cfbb9c57e1 <JS Function SourceNode (SharedFunctionInfo 0x2793deb41371)>,w=0x2ec39bd3f701 <JS Array[528671]>,x=528671)
    2: forEach [native array.js:~954] [pc=0x2b91ba17b136] (this=0x2ec39bd3f701 <...

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
 1: node::Abort() [node]

Seems like we're hitting limits of node --max_old_space_size in jenkins. The workarounds for this that I've found is to increase the limit
so that we still fit to it. Unfortunately webpack-rails doesn't provide a way how to change this and as it's not maintained anymore,
the proper fix means switching to webpacker (or something else).

As a short-term fix, we can probably provide our own webpack:compile task and set the required value there.