Uploading a large amount of data results in high memory usage on CI service

Note: please note that Liferay has renamed its Liferay Experience Could offerings to Liferay SaaS (formerly LXC) and Liferay PaaS (formerly LXC-SM).

Issue

• Uploading more than 1 GB worth of files can result in a failed build and high memory usage indicated by an exit value of 137 error.
• Here's how to print the output showing the amount of data that Liferay PaaS is uploading:
  1. Navigate to the ci folder and rename file "#Jenkinsfile-before-cloud-build" to "Jenkinsfile-before-cloud-build".
  2. Add the following line to the ci/Jenkinsfile-before-cloud-build file: sh "du -h build/"

Environment

• Liferay PaaS

Resolution

• The high memory usage is likely due to the Nodejs library used by the lcp command. By setting the following environment variable in your CI service's LCP.json, the lcp command would use the native git CLI instead of the Nodejs library, which could help resolve this issue:

  • "env": {
      "LCP_CI_CLI_USE_EXTERNAL_GIT": "use-external-git"
    }

Additional Information

• How to resolve Jenkins failing to build a service in LXC with a non-zero exit value of 137