Legacy Knowledge Base
Published Jul. 2, 2025

Git Branch configuration with Liferay Cloud Dev environment

Written By

Sivakumar Perumal

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.

Issue

  • Is there any place where the "develop" branch is configured as a default branch?

Environment

  • Liferay Cloud

Resolution

  • The environment variable LCP_CI_DEPLOY_BRANCH is read on the ciservice is responsible for the configured branch. One can change the LCP_CI_DEPLOY_BRANCH value (default is develop)
  • Why the default is develop?
    The entrypoint script for Jenkins in the ci service is responsible for the default branch. If no value is provided, it defaults to “develop”.
    if (env.BRANCH_NAME == env.LCP_CI_DEPLOY_BRANCH) {
    deployToCloud(deployBranch: env.LCP_CI_DEPLOY_BRANCH, deployTarget: env.LCP_CI_DEPLOY_TARGET)
    }

Additional Information

Did this article resolve your issue ?

Legacy Knowledge Base