Applicable to:
- Plesk Onyx for Linux
Symptoms
- Additional deployment actions in the Git extension are called despite the branch specified in the webhook: even if commits are performed to another branch.
- Remote Git repository with several branches (for example, from GitHub) is connected to the domain in Plesk.
- The master branch is selected in the repository.
- Additional deployment actions are set in the Repository Settings in Plesk.
- Webhook is created on GitHub (or another Git hosting) for push event.
Cause
This is a bug with ID EXTGIT-64 which is planned to be fixed in future Plesk updates.
Resolution
Currently, no workaround is available.
Comments
4 comments
Any news on when this bug will be fixed?
@Bruno
Hello!
The issue is under investigation. Currently, there is no ETA.
To be notified when the bug will be fixed, click the "Follow" button.
Hi Ivan, this has been discussed quite a bit at GitHub https://github.com/gitlabhq/gitlabhq/issues/1176 and the only way to make it work is by filtering from the json sent by the webhook.
The "ref" value will include the branch name to allow the filtering. For example with master branch it will look like this:
I'm really looking forward being able for devs to be able to commit changes to their sites without needing to access the plesk panel to deploy or asking me to do it for them.
@Bruno
Hello!
Thank you for this additional information.
Plesk Development Team does its best. This article will be updated after the issue fix would be released.
Please sign in to leave a comment.