[Bug]: out of memorry errors in CICD pipelines freqent for large third party dependencies

[SteveKrisjanovsD365]

AL-Go version

6.3

Describe the issue

we're currently building an appsource app that exends appsource app LS Central (Publisher: LS Retail).

50% of the time CICD fails at the build step due to out of memory errors (LS for BC takes a large resource footprint). Currently we re-run the failed job(s) and cross our fingers.

Short of exploring self-hosted runners, is there anything that can be done to improve CICD reliability?

Expected behavior

CICD succeeds without any out of memory errors

Steps to reproduce

create an app that depends on LS Central

Additional context (logs, screenshots, etc.)

No response

[freddydk]

Could you include the log, so that we can determine whether you are using containers or compilerfolders?
Also the log will tell us how much memory is used.
If you are using containers, you could try to add a setting called "MemoryLimit": "16G" - or like - but without the log, it is hard to determine whether this will solve anything.

[SteveKrisjanovsD365]

alas I'm re-running the failed job(s) so I don't have a failed log to attach. if it fails again I'll attach the log.,

We are definately using containers however and NOT compilerfolders

wer'e aware that LS Central for BC has a huge memory footprint (both onprem and saas) which has presented its own chalenges in the past when too many onprem instances on a server have LS installed and onprem BC shell experiences frequent out of memory errors if there are too many instances with LS installed.,

[freddydk]

In github, you can select the prior re-run in the top right corner and see the log from the failing builds.

[SteveKrisjanovsD365]

duly noted!

[SteveKrisjanovsD365]

@freddydk

while I wait for the CICD to finish with the memorylimit set to 16G, I found an older log that has the out of memory exception. see attached. in the log zip it's the "CA" project that failed @ build step with out of memory

logs_35243457639.zip

[SteveKrisjanovsD365]

FYI - setting the memorylimit to 16G worked. pipelines that were prone to failing are no longer erroring out