[Bug 288595] www/gitlab upgrading to 18.2.1 fails

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288595

            Bug ID: 288595
           Summary: www/gitlab upgrading to 18.2.1 fails
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: mfechner@FreeBSD.org
          Reporter: jontheil@gmail.com
          Assignee: mfechner@FreeBSD.org
             Flags: maintainer-feedback?(mfechner@FreeBSD.org)

I have been using the port without any issues for quite a long time. But I can
no longer update the software as described in
https://gitlab.com/mfechner/freebsd-gitlab-docu/-/blob/master/update/18.1-18.2-freebsd.md?ref_type=heads.
I'm not absolutely sure, but I think the issues started at this point (18.1 =>
18.2).
One obvious problem is that I get the error message
"FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed -
JavaScript heap out of memory"
and that the path /usr/local/www/gitlab/public/assets/webpack/ remains empty.
I have tried several things to mitigate this. Obviously, I have shut down any
programs/servers not needed. I have tried to use
setenv NODE_OPTIONS "--max-old-space-size=3584"
at the beginning or by using
su -l git -c "cd /usr/local/www/gitlab && RAILS_ENV=production
NODE_ENV=production USE_DB=false SKIP_STORAGE_VALIDATION=true
NODE_OPTIONS='--max-old-space-size=3584' bundle exec rake
gitlab:assets:compile"
I have made shell scripts for both major and patch updates.
When I watch the script, I see

yarn run v1.22.19
$ NODE_OPTIONS="${NODE_OPTIONS:=--max-old-space-size=5120}" webpack --config
config/webpack.config.js

so the setting seems not to be used. What would be the correct setting inside a
sh script?
There have been other issues but I think I need to overcome the memory issue
first.

-- 
You are receiving this mail because:
You are the assignee for the bug.