Note: please note that Liferay has renamed its Liferay Experience
Could offerings to Liferay SaaS (formerly LXC) and
Liferay PaaS (formerly LXC-SM).
Issue
- When deploying multiple environments to Liferay Cloud, the LCP.json file is used to define multiple separate Liferay major versions for the different environments.
Environment
- Liferay PaaS
Resolution
- For deploying with Liferay Cloud, since there is only one gradle.properties file for a build (where the Liferay image is defined), the LCP.json file cannot be used to define multiple separate Liferay major versions
- The Liferay image version should match between the LCP.json file and the gradle.properties file and the gradle.properties file can only define one image at a time. When a build is submitted to CI/Jenkins, it configures the build in such a way that it could be deployed on any of the environments in a project, so the build needs to be tenable for all environments (at least as far as the LCP.json image value always matching the gradle.properties file).
- If a build is intended to only be deployed in one environment, it is best practice to add descriptive titles to builds so they are not confused during deployment.
- One way to have multiple environment setups using different major Liferay versions is to set up multiple branches in your Git repository to separate the builds (e.g. one for upgrade testing, one for primary deployment, etc.).