Allow webhook subscriptions for tag events
Currently repo hooks using the webhook service type can only subscribe to "push" events. These hooks however do not fire if a new tag is pushed to a repo, only when new commits are added. I would like to be able to receive tag creation events in my webhook, so that I could trigger CI events for them downstream. This would enable e.g. automatic releases of tagged versions while supporting developer workflows where tags are pushed after the commits.
We have released this functionality as part of Deveo 3.20. Deveo now supports triggering webhooks on Git repositories for commit, branch and tag related events.
You can configure the triggers from the hooks view as briefly covered in our release blog post:
Please refer to our User’s Guide to see an example of the payloads for each trigger:
AdminDeveo Support (Support, Deveo) commented
thanks for the comment. This feature was indeed included as part of Deveo 3.20. Your assumption of the payload is correct.
We've updated the docs both on UserVoice's knowledge base and on app.deveo.com. In the future, we recommend checking https://app.deveo.com/docs/user/ for the most up-to-date information.
Jonne Nauha commented
Deveo: Has this been implemented?
I'm seeing a new option in the webhook UI "Trigger when a tag is created or deleted" but no explanation what the tag payloads might be at http://support.deveo.com/knowledgebase/articles/494691-using-deveo-webhooks
Could you please update that page with a example of the payload for a tag create/delete event. The unknown part is how to know if its a tag or normal push event. Will it just have "ref" as "refs/tags/<tag>"?
Jonne Nauha commented
+1. I'm have a custom build bot server that needs tag events. We need this to do automated build and deploy of releases (that we do via tags).
Please make the "ref" prop in the webhook POST data "refs/tags/<tag>" like github and others do.
Please also mark your "created" to true if its a new tag, and to false when existing tag was updated.
Othewise keeping the data same as normal commit push would be good. The "refs/tags/<tag>" can be used to detect if it is a tag or normal commit to a branch. And the tag name can be parsed from <tag>.