Service Updates for Liferay Cloud
The services update for 10/10/2024 is a minor update for CI service.
DXP Cloud Stack
| Service Name | Previous Release | Current Release | Docker Images |
|
Backup |
5.21.0 |
5.22.0 |
liferaycloud/backup:5.22.0 |
|
CI |
5.2.7 |
5.3.0 |
liferaycloud/jenkins:2.356-jdk8-5.3.0 |
|
Database |
5.5.2 |
5.6.0 |
liferaycloud/database:5.6.0 |
| Liferay |
5.8.2 |
5.8.3 |
liferaycloud/liferay-dxp:7.4-5.8.3 |
|
Search |
5.3.1 |
5.3.2 |
liferaycloud/elasticsearch:8.15.1-5.3.2 liferaycloud/elasticsearch:7.17.23-5.3.2 |
|
Webserver |
6.1.3 |
6.1.4 |
liferaycloud/nginx:1.24.0-6.1.4 |
Change Log
| Service Name | Service Version | Ticket No. | Description |
|
CI |
5.3.0 |
LCD-38659 |
Add support for Client Extensions on PaaS |
| LCD-40895 | Add support to change JDK version via Environment Variable | ||
| LCD-40896 | Add JDK17 and JDK21 compatibility to CI build pipelines | ||
| LCD-36037 | Fix: Reduce default Jenkins Executors to fix OOM issues |
Note :
LCD-40896 Introduces JDK17 and JDK21 for use by customer’s DXP Cloud build (specifically the liferay service build portion). Existing JDK8 and JDK11 are still available.
Jenkins itself in version 5.3.0 still runs on JDK8
LCD-40895 Until now if a customer wanted to change the JDK for build pipelines from the default JDK8 to JDK11(or another JDK) they have to modify the gradle.properties in the liferay gradle workspace. Now customers will be able to do it by configuring the following Environment Variable to specify which JDK they want to use.
"LCP_CI_GRADLE_JDK": "jdk11/jdk17/jdk21"
We recommend customers to stop using gradle.properties and switch to using this environment variable instead. The older jdk paths will soon be deprecated.
LCD-36037 This reduces the default executors to 1 which means by default all build will be processed serially. If a customer wishes to increase the number they can do so by using the following environment variable
LCP_CI_NUM_EXECUTORS to the integer they wish. 1,2,3, etc
However, increasing the default number of executors might increase the chances of failed builds due to the default memory constrains we have on our CI service. You will see a better outcome if you increase the memory against CI service when increasing the default number of executors.
We will be working towards making the CI service more efficient in future.
If you do run into any issues, please feel free to open a support ticket and we will help address your issues as soon as possible.
Update Instructions
Note : To take advantage of the new features and fixes provided by the 5.x stack of services, you must update your entire stack to the new 5.x images.
Image Update Instructions
The Liferay Cloud image versions needs to be set inside of the <service>/LCP.json file.
Note, however, that the liferay service uses two image properties. The DXP Cloud image is set in the liferay/LCP.json file, but the liferay/dxp image is set in the gradle.properties. This change was made in order to facilitate easier deployment using the Liferay Cloud CLI.
liferay/LCP.json file would set the liferaycloud/liferay-dxp image:
"image":"liferaycloud/liferay-dxp:7.4-5.X.X"
liferay/gradle.properties file would set the liferay/dxp image:
liferay.workspace.docker.image.liferay=liferay/dxp:2024.q1.1
For all other images, you will just need to update the LCP.json file with the intended image version.
Once the LCP.json files are updated, commit the changes to your Git repository.
git add . && git commit -m "Update dxp cloud stack to XXX"
After pushing these changes to the remote repository, a build will be created in Liferay Cloud and it is ready to deploy.