Submit Feedback
Legacy Knowledge Base
Published Jun. 30, 2025

Jenkins builds failing in Liferay Paas

Written By

Jorge García Jiménez

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

  • Jenkins builds are failing. We can see below trace in ci logs 
    okhttp3.internal.platform.Platform log
    WARNING: A connection to https://api.github.com/ was leaked. Did you forget to close a response body? To see where this was allocated, set the OkHttpClient logger level to FINE: Logger.getLogger(OkHttpClient.class.getName()).setLevel(Level.FINE);

Environment

  • Liferay Paas with ci (liferaycloud/jenkins:2.356-jdk8-5.1.0) and Github

Resolution

  • This error is shown because Github token is expired. After refreshing the token and configuring the new value in LCP_CI_SCM_TOKEN environment variable it should work again.

 

 

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?