Legacy Knowledge Base
Published Jul. 2, 2025

Liferay PaaS deployment stuck at jenkins

Written By

Anishq Sharma

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

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

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability 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

  • Deployment gets stuck at jenkins with below error:
     stderr: fatal: Unable to create '/var/jenkins_home/workspace/xyz_prd/.git/shallow.lock': File exists.
     Another git process seems to be running in this repository, e.g.
     an editor opened by 'git commit'. Please make sure all processes
     are terminated then try again. If it still fails, a git process
     may have crashed in this repository earlier:
     remove the file manually to continue.

Environment

  • Liferay DXP 7.1
  • Liferay DXP 7.2
  • Liferay DXP 7.3
  • Liferay DXP 7.4

Resolution

  • The issue is observed when a deployment gets failed due to memory/ other reasons and workspace auto-cleanup job is not completed successfully.
  • Issue should be resolved automatically after running a new build, as workspace gets cleaned up after every build completion.
  • In case the issue still persists, kindly create a support ticket mentioning the same.
Did this article resolve your issue ?

Legacy Knowledge Base