Submit Feedback
Legacy Knowledge Base
Published Jun. 30, 2025

Jenkins build fails with "LCP.json with id "undefined" is not valid against the schema" error

Written By

István Gergely-Tárnoki

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

  • Our new build is failing in Jenkins with the following error:
Failed to deploy the services in /var/jenkins_home/workspace/<workspace_name>/build on liferay.cloud.
Reason: Unexpected message when uploading services: 
LCP.json with id "undefined" is not valid against the schema

Environment

  • Liferay PaaS

Resolution

  • You should check your LCP.json files because a property might need to be relocated
  • Most of the time the property is out of the environment's scope and should be placed in the "env": {} section, like
  • From
"environments": {
   "infra": {
     "deploy": true,
     "PLUGINS_FORCE_UPGRADE": "true"
   }
  • To
"environments": { 
   "infra": { 
     "deploy": true, 
     "env": { 
       "PLUGINS_FORCE_UPGRADE": "true" 
           } 
      } 
}
Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?