Submit Feedback
Legacy Knowledge Base
Published Jun. 30, 2025

Jenkins builds are failing due to an exit value of 137

Written By

Pooja Bhambani

How To articles are not official guidelines or officially supporteddocumentation. They are community-contributed content and may not alwaysreflect the latest updates to Liferay DXP. We welcome your feedback toimprove How to articles!

While we make every effort to ensure this Knowledge Base is accurate, itmay not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with anyfeedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack"publication program, made available for informational purposes. Articlesin this program were published without a requirement for independentediting or verification and are provided "as is" withoutguarantee.

Before using any information from this article, independently verify itssuitability for your situation and project.
Note: please note that Liferay has renamed its Liferay Experience Could offerings to Liferay SaaS (formerly LXC) and Liferay PaaS (formerly LXC-SM).

Issue

  • After adding the 'hostAliases' in the environment, the Jenkins builds are failing with the below error: 
    ERROR: the command "[ lcp, deploy, --only build, ----]" had an exit value of 137. 

Environment

  • Liferay PaaS
  • Liferay DXP 7.4

Resolution

  • When Jenkins builds fail due to an exit value of 137, it means a container or pod is trying to use more memory than it's allowed.
  • Increase the Gradle memory by using the following environment variable:
    LCP_CI_GRADLE_JVM_ARGS": "-Xmx4g -XX:MaxMetaspaceSize=512m -XX:+HeapDumpOnOutOfMemoryError -Dfile.encoding=UTF-8
Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?