This services update is for the Major version update from 3 to 4

Version Compatibility between 3 and 4

All of the Version 4 Liferay Cloud service images are compatible with the older workspace structure except for Liferay. Due to the multi-stage build process used by the version 4 images for liferay, it is not compatible with the old workspace. However, you can use the other version 4 images even in the old workspace.

In order to use the Liferay service version 4, you need to update your project workspace. For details on updating your project please see this guide. If you want to find out more about the new features that are offered through the services please go here.

Choose the Right liferay/dxp Docker image

The Version 4 Liferay service allows the end user to specify the fix pack level through the liferay/dxp docker images.

When choosing an image please use a fully qualified version with a timestamp.

Please use this tag:

liferay/dxp:7.2.10-sp2-202005120922

Instead of this one

liferay/dxp:7.2.10-sp2

The docker tags without the timestamp are rolling tags that update frequently. However, due to aggressive image caching, you may not receive the latest version of that tag when specifying it as your base liferay image. In order to avoid caching issues, always use the tag with a timestamp suffix.

you specify the liferay tag through the gradle.properties file in your /liferay folder.

The minimum compatible liferay/dxp version for liferaycloud/liferay-dxp:7.2-4.0.0 is sp1 (ga1 or fp1 will not successfully establish a cluster).

CI Service Default Jenkinsfile

In the Version 3 image of CI, the built-in Jenkinsfile (starting with version 3.2.0) is not enabled automatically. However, in the switch to the Version 4 images, the built-in Jenkinsfile is enabled by default. If you want more information about the built-in Jenkinsfile please go here.

Also, since the version 4 images are expecting the updated project workspace, the path for the Jenkinsfile hooks is defaulted to 'ci' instead of 'lcp/ci'. If you are intending to use the version 4 of CI with the old project structure you will need to set the following environment variable:

LCP_CI_SCM_JENKINSFILE_HOOKS_DIR="lcp/ci/"

Version 4 DXP Stack 2020.21.1

Service Name	Current Release	Docker Images
Backup	4.0.0	liferaycloud/backup:4.0.0
CI	4.0.0	liferaycloud/jenkins:2.222.1-4.0.0
Database	4.0.0	liferaycloud/database:4.0.0
Liferay	4.0.0	liferaycloud/liferay-dxp:7.2-4.0.0 liferaycloud/liferay-dxp:7.1-4.0.0 liferaycloud/liferay-dxp:7.0-4.0.0
Search	4.0.0	liferaycloud/elasticsearch:6.8.6-4.0.0 liferaycloud/elasticsearch:2.4.6-4.0.0
Webserver	4.0.0	liferaycloud/nginx:1.16.1-4.0.0

 

 Update Instructions

Only Applicable to Version 4 Images

After upgrading your project using this guide, the Liferay Cloud image versions are no longer set with the gradle.properties file. They are specified inside of the LCP.json directly in order to facilitate easier deployment using the Liferay Cloud CLI. Apply these image updates directly to the LCP.json files

Once the LCP.json files contains the updates, commit the changes to your Git repository.

git add gradle.properties && git commit -m "update dxp cloud stack to 2020.22.1"

After pushing these changes to the remote repository, a build will be created in Liferay Cloud and it is ready to deploy.