-
-
Notifications
You must be signed in to change notification settings - Fork 373
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release event not working as expected #3666
Comments
Which filters (except event) do you have set? |
The webhook that is created by Woodpecker 2.5 does not include the "release" type in gitea. When manually adding this type to the webhook, woodpecker is triggered as expected. |
Seems to be actually missing: https://github.com/anbraten/woodpecker/blob/62ae7b2e213d861bbc6c61154b266066f1e92f9c/server/forge/gitea/gitea.go#L386
That's expected as both a different events. |
Even though this event is missing this seems to be not the problem of the issue. Take a look at the screenshot - the hook is sent from a release event |
I tested the release, worked for me in a pipeline with 2.4.1 and 2.5
|
Tested with gitea 1.21.7 and WP 2.6.0, both freshly installed. Works like a charm. The latest gitea 1.22 (about two weeks young) mentions as enhancement in the changelog:
Maybe this leads to problems. I will try to test it with a fresh setup with gitea 1.22 |
@xoxys Do you still have issues with the release event? |
I can try to reproduce it on the weekend. Im also fine to close this issue for now and only re-open it if Im able to. |
closing for now |
Thanks, sorry for not providing feedback till now. Ill reopen it of I find some time to test it. |
Component
server
Describe the bug
release
events result in an empty pipeline even if no event filter is set in the workflow:I've only tested it with gitea/forgejo this might affect other forges as well.
System Info
Additional context
No response
Validations
next
version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]The text was updated successfully, but these errors were encountered: