Submit Feedback
Legacy Knowledge Base
Published Jun. 30, 2025

Deploying to an Existing Build via CLI Tool

Written By

Pablo Vidal

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

  • The user wants to know if it is possible to deploy to an existing build using the Liferay Cloud CLI tool. The idea would be to use a command like this:

    lcp deploy --project=[project_name] --environment=[dev/uat/prd] --build-id=[xyz

Environment

  • Liferay PaaS

Resolution

  • Currently, the Liferay Cloud CLI does not support deploying an existing build directly using a build ID
  • The deployment process is designed to work with builds generated locally or through an integrated CI/CD pipeline.

Additional Information

  • In this case, we are dealing with a product limitation, however, this issue has already been formally addressed to our team responsible for implementing new features through Feature Request LPD-26368.
  • If this idea is aligned with the development roadmap, it may be implemented in a future release.

  • For more details on using the CLI tool, see: Command-Line Tool

 

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