Liferay Cloud Infrastructure

Volver a Services Changelog

2020.10.13 Services Update 2020.42.1

Service Updates for Liferay Cloud Version 3 and 4

The services update to 2020.42.1 includes updates to the Backup, CI, Database, Liferay, Search and Webserver services.

 

liferay/dxp docker image tags

In an ever evolving effort to provide the best support, the docker tags on liferay/dxp docker repository have changed. The new addition is a `-dx.y.z` designation (e.g. -d1.0.2), which provides information about any changes to the underlying docker scripts that are utilized by the image. The new tags on Dockerhub for liferay/dxp are formatted as follows

liferay/dxp:{Liferay.DXP.Version}-{Patching-Level}-{Docker.Script.Version}-{Timestamp}
liferay/dxp:7.2.10-dxp-7-d1.0.0-202009071842

When selecting which liferay/dxp base image to utilize for your project, please consider the entire docker tag, and please be sure to check out the release notes for your patching level before applying to your environment: DXP Release Notes

 

Disk Usage In CI Service

Disk usage is an important part of the build process. To mitigate issues with running out of disk we have provided a way to see the current disk usage of the CI service. Log into the Jenkins Service and then you should see an option for "Disk Usage" on the sidebar navigation. 

When navigating to this tab you will be presented a breakdown of the disk usage of the Jenkins home directory and sub directories.

Most project are provisioned with the default disk space, which means that performing lots of builds with many different branches/ pull requests can quickly consume the available disk. To mitigate this behavior please consider setting the following configurations in your CI service (depending on your projects workflow/needs).

LCP_CI_SCM_BRANCH_FILTER_INCLUDE=master develop

LCP_CI_SCM_BRANCH_FILTER_EXCLUDE=PR-*

the first configuration would only allow building the master and develop branches, while the second configuration would exclude all pull request builds. This can significantly save space on the CI service without hampering the review process

Note: these configurations are targeted to GitHub since that is the default SCM provider

 

Log Level Configuration for CLI in CI service

It is now possible to specify the CI service to use the --verbose flag when performing any lcp commands. 

This provides greater debugging and investigation potential when encountering failing builds. 

LCP_CI_CLI_LOG_LEVEL=verbose

Only the --verbose log level is currently supported in the CLI, but as more log levels are added, this property will be updated to support it.

Version Compatibility between 3 and 4

For details on service compatibility between version 3 and 4 please see release update 6/11/2020 Services Update 2020.24.1 or 5/28/2020 Services Update 2020. 22.1 

 

Feature Exclusion in Version 3 DXP Stack

Due to the deprecation process for the Version 3 DXP Stack, the 3.x service images will no longer receive feature updates.

The direct impact of this change is that the search service support for elasticsearch 7.x is not offered  as a 3.x search image. 

Up to this point, all features and fixes have been applied to both the 3.x and 4.x service images (with some exclusions when appropriate). From this point forward, only bug fixes will be applied to the 3.x service versions.

 

Version 4 DXP Stack 2020.42.1 

Service Name Previous Release Current Release Docker Images

Backup

4.0.5

4.0.8

liferaycloud/backup:4.0.8

CI

4.0.5

4.0.7

liferaycloud/jenkins:2.235.5-4.0.7

Database

4.0.4

4.0.6

liferaycloud/database:4.0.6

Liferay

4.0.4

4.0.6

liferaycloud/liferay-dxp:7.2-4.0.6

liferaycloud/liferay-dxp:7.1-4.0.6

liferaycloud/liferay-dxp:7.0-4.0.6

Search

4.0.0

4.0.1

liferaycloud/elasticsearch:7.9.1-4.0.1

liferaycloud/elasticsearch:6.8.6-4.0.1

liferaycloud/elasticsearch:2.4.6-4.0.1

Webserver

4.0.1

4.0.2

liferaycloud/nginx:1.16.1-4.0.2

 

Version 4 Update Instructions

Only Applicable to Version 4 Images

After upgrading your project using this guide, the Liferay Cloud image versions are no longer set inside of the gradle.properties file. They now need to 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.2-4.0.6"

liferay/gradle.properties file would set the liferay/dxp image:

liferay.workspace.docker.image.liferay=liferay/dxp:7.2.10-dxp-7-d1.0.0-202009071842 

Once the LCP.json files are updated, commit the changes to your Git repository.

git add . && git commit -m "update dxp cloud stack to 2020.42.1"

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

Version 4 Change Log

Service Name Service Version Ticket Number Description

Backup

4.0.8

LCD-7579

add retry to download to mitigate random network failures

 

4.0.6

LCD-7850

update vulnerable dependencies

CI

4.0.7

LCH-1794

GRADLE_OPTS has unnecessary default since the daemon gradle jvm is controlled via gradle.properties

 

LCH-1860

Add configurable log level for the CLI

 

4.0.6

LCD-8244

Show disk space in Jenkins

Database

4.0.6

LCD-8538 

expand granular configuration of database properties

 

4.0.5

LCD-7850

update service dependencies

Liferay

4.0.6

LCH-1858

update setenv file to allow jdk11

 

LCH-1789

remove carriage return and trim when reading portal properties files

LCH-1788

ignore commented properties when reading jdbc settings from portal properties files

 

4.0.5

LCH-1689

unable to remove trial license from liferay/dxp base image

Search

4.0.1

LCD-6832

Add support for ES 7.x (7.9.1)

Webserver

4.0.2

LCD-7278

increment HAProxy version to 2.x

 

Version 3 DXP Stack 2020.42.1

Service Name Previous Release Current Release Docker Images

Backup

3.2.17

3.2.19

liferaycloud/backup:3.2.19

CI

3.2.9

3.2.10

liferaycloud/jenkins:2.235.5-3.2.10

Database

3.2.13

3.2.15

liferaycloud/database:3.2.15

Liferay

3.0.28

3.0.29

liferaycloud/liferay-dxp:7.2.10-sp1-fp7-3.0.29

liferaycloud/liferay-dxp:7.1.10-ga1-fp18-3.0.29

liferaycloud/liferay-dxp:7.0.10-ga1-fp93-3.0.29

Search

3.0.8

3.0.8

liferaycloud/elasticsearch:6.8.6-3.0.8

liferaycloud/elasticsearch:2.4.6-3.0.8

Webserver

3.2.1

3.2.1

liferaycloud/nginx:1.16.1-3.2.1

 

Version 3 Update Instructions

To apply these updates, update the gradle.properties file the project root folder with the new docker image tags. Here is an example of applying update 2020.42.1 for a 7.2 Liferay project:

liferay.workspace.lcp.backup.image=liferaycloud/backup:3.2.19
liferay.workspace.lcp.database.image=liferaycloud/database:3.2.15
liferay.workspace.lcp.search.image=liferaycloud/elasticsearch:6.8.6-3.0.8
liferay.workspace.lcp.liferay.image=liferaycloud/liferay-dxp:7.2.10-sp1-fp7-3.0.29
liferay.workspace.lcp.webserver.image=liferaycloud/nginx:1.16.1-3.2.1
liferay.workspace.lcp.jenkins.image=liferaycloud/jenkins:2.235.5-3.2.10

Once the gradle.properties file contains the updates, commit the changes to your Git repository.

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

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

 

Version 3 Change Log

Service Name Service Version Ticket Number Description

Backup

3.2.19

LCD-7579

Retry the file download on google storage

CI

3.2.10

LCD-8244

Show disk space in Jenkins

 

LCH-1794

GRADLE_OPTS has unnecessary default since the daemon gradle jvm is controlled via gradle.properties

LCH-1860

Add configurable log level for the CLI

Database

3.2.15

LCD-8538

expand granular configuration of database properties

Liferay

3.0.29

LCH-1858

update setenv file to allow jdk11

 

LCH-1789

remove carriage return and trim when reading portal properties files

LCH-1788

ignore commented properties when reading jdbc settings from portal properties files

 

On this page