• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Question Continuous deployment with GitLab CI/CD

devnull

New Pleskian
Server operating system version
Ubuntu 20.04.5 LTS
Plesk version and microupdate number
Plesk Obsidian 18.0.48
Hey guys,

I deploy many web apps on Plesk with the Git feature.

It works well most of the times but I feel bad about errors and reverting deployment when something went wrong.
Unfortunately I am missing the good integration of pipelines etc. is not given when using GitLab actions. Additionally I cant define the CD commands in my code (e.g. .gitlab-ci.yml).

Has someone already integrated the "traditional" deployment using a gitlab runner along Plesk? Would be great to discuss a little bit about the pitfalls and best practise.
 
Back
Top