无需使用控制面板部署并修改Liferay Portlet的方案咨询

Hey, glad you're diving into Liferay Portlet development! Since you already have an automated CI/CD pipeline with Jenkins and Puppet, here are the best UI-free deployment strategies that fit right into your existing workflow:

1. Drop artifacts into Liferay's watch deploy directory (simplest approach) #

Liferay comes with a built-in hot-deployment mechanism that monitors the [LIFERAY_HOME]/deploy folder. Any WAR/JAR portlet artifact placed here will be automatically detected, unpacked, and deployed by Liferay.

This fits perfectly with your existing Puppet setup: after Jenkins builds the artifact, configure Puppet to copy the file directly to the deploy directory on your target Liferay servers. Just make sure the Liferay runtime user has read/write permissions on this folder. For updates, simply push the new version—Liferay will handle replacing the old portlet (no manual UI steps needed).

A quick heads-up: if your portlet has major changes like database schema updates or new dependencies, you might need to restart Liferay/JBoss after deployment. You can add this restart step to your Puppet or Jenkins pipeline if needed.

2. Use Liferay's REST API for programmatic control #

If you want more flexibility (like checking deployment status, rolling back, or integrating with custom pipeline logic), Liferay's REST API is a great option. You can call it directly from your Jenkins pipeline or a shell script to upload and deploy portlets without touching the UI.

Here's a sample curl command to deploy a portlet via API:

curl -X POST \
  -u "your-admin-username:your-password" \
  -F "file=@your-portlet-artifact.war" \
  http://your-liferay-server:8080/o/api/v1.0/apps

Make sure your Liferay instance has API access enabled, and the CI/CD server can reach the API endpoint. You can also use this API to list deployed apps, delete old versions, or check deployment status—super useful for complex pipelines.

3. Integrate with your existing JBoss deployment workflow (if applicable) #

Since you're already pushing artifacts to JBoss via Puppet, you might wonder if you can deploy portlets directly to JBoss's deployments folder. While technically possible, it's not the recommended approach—Liferay handles extra steps like portlet registration, permission setup, and integration with its core platform that JBoss won't manage.

Sticking with Liferay's deploy directory is safer, but if you must align with JBoss deployment, ensure you've configured Liferay's module system correctly to recognize the portlet from JBoss's deployments.

Key Tips for Smooth Automated Deployment #

• Version your artifacts: Always include unique version numbers in your portlet WAR/JAR filenames (e.g., my-portlet-1.2.3.war). This helps Liferay detect new versions immediately and avoids caching issues.
• Test hot-deployment first: Before rolling out to production, test that your portlet updates work via hot-deployment—some complex portlets might require a restart, so plan for that in your pipeline.
• Lock down permissions: Make sure the service account used by Puppet/Jenkins has only the necessary permissions (e.g., write access to deploy folder, API admin rights) to follow security best practices.

内容的提问来源于stack exchange，提问作者Chris Williams