You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have an on-prem gitea instance connected with on-prem AppVeyor server. AppVeyor can't create new builds if commits and head_commit are empty, see also open issue on AppVeyor: appveyor/ci#3765
Screenshots
No response
The text was updated successfully, but these errors were encountered:
Just tested newest Gitea main build (1.16.0+dev-785-g496acbe9e) and AppVeyor is still not triggering a new build for a new tag. AppVeyor seems to expect both commits and head_commit to be defined.
@KN4CK3R AppVeyor Server was updated with version 7.0.3134 to support head_commit in the webhook payload. With that change AppVeyor Server is creating a build for a Gitea tag webhook again. See also appveyor/ci#3765.
Thanks for fixing the Gitea part!
Gitea Version
1.15.8
Git Version
2.33.1
Operating System
Windows Server 2016
How are you running Gitea?
based on gitea-1.15.8-windows-4.0-amd64.exe as Windows Service
Database
SQLite
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Description
Creating a new tag for a gitea repo creates a webhook with empty
commits
andhead_commit
. See example from gitea demo site:I have an on-prem gitea instance connected with on-prem AppVeyor server. AppVeyor can't create new builds if
commits
andhead_commit
are empty, see also open issue on AppVeyor: appveyor/ci#3765Screenshots
No response
The text was updated successfully, but these errors were encountered: