Configure Client Extensions Code with Github and Jenkins

Note: please note that Liferay has renamed its Liferay Experience Could offerings to Liferay SaaS (formerly LXC) and Liferay PaaS (formerly LXC-SM).

Issue

• Is it possible to deploy local code to the Liferay SaaS Cloud environment via Jenkins? 

• If users want to maintain the code in Github then which project structure do they need to follow as part of GitHub?

Environment

• Liferay SaaS

Resolution

• All of the Liferay cloud consumers have access to an extensions environment where Client Extensions can be deployed and linked with their Liferay SaaS environment.
• Although a CI service is not present in the extension environment, therefore, users will have to incorporate the lcp deploy commands into their own external CI tool.
• Liferay cloud (Liferay SaaS offering) consumers can only access the Cloud Console for their Client Extensions environments. This means that users cannot view logs, restart, deploy, or otherwise manage services on the production project.
• CI, Backup, Database, Liferay, Search, and Webserver are all inaccessible to the users. However, if information is needed, or an action needs to be performed on the Cloud Console, it should be requested by users via support tickets.
• As a result, this request is not achievable at this time (At the time of publishing this article)

Additional Information

• Please submit a support ticket in case any more information is required related to this process.