Versioning of Hook plugins and custom portlets

[G R Rajesh Babu, modifié il y a 8 années.]

Hello All,

We are currently developing different hooks and custom portlets in 6.2 and wanted to apply the version control to the portlets in Liferay itself so that the admin can select the required version of the portlet that should go live, Similar to WCM portlets which can be modified, approved and make live via workflow on Staging and Go Live.

Any Pingbacks on availability of this feature for the Hooks and custom plugin portlets.

Regards,
Rajesh.

[Olaf Kock, modifié il y a 8 années.]

Does this mean you want to version control Liferay's portlets - e.g. third party? Or do you want to put your own plugins under version control?

For your own code: Go ahead, use the version control of your least distrust. For Liferay's plugins: Technically they're already under source control - check github.com/liferay. But there are other plugins, third party and - in case you're on EE - the EE plugins, that are not available and can't or shouldn't be compiled yourself. This is in the realm of classic configuration management and you should look at those options. It's largely a matter of how you're going to maintain your server, not so much a feature of Liferay

[G R Rajesh Babu, modifié il y a 8 années.]

Olaf Kock:

Does this mean you want to version control Liferay's portlets - e.g. third party? Or do you want to put your own plugins under version control?

For your own code: Go ahead, use the version control of your least distrust. For Liferay's plugins: Technically they're already under source control - check github.com/liferay. But there are other plugins, third party and - in case you're on EE - the EE plugins, that are not available and can't or shouldn't be compiled yourself. This is in the realm of classic configuration management and you should look at those options. It's largely a matter of how you're going to maintain your server, not so much a feature of Liferay

Hi Olaf,

Thanks for your reply. It is for my own code only.

[Olaf Kock, modifié il y a 8 années.]

Ok, just go ahead and define procedures - like tagging, continuous integration or whatever you like - and document that to your system administrators. Not sure what exactly the problem is? Any source code can be under version control and the build- and administrative procedures are standards outside of Liferay.

[G R Rajesh Babu, modifié il y a 8 années.]

Olaf Kock:

Ok, just go ahead and define procedures - like tagging, continuous integration or whatever you like - and document that to your system administrators. Not sure what exactly the problem is? Any source code can be under version control and the build- and administrative procedures are standards outside of Liferay.

Yeah. I have to maintain the version control of the portlets in liferay (similar to document version control) where in we need to give the advantage to the admin to select any available previous version of the portlet that should be displayed in the Live environment as and when required.