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 am using Gitea in combination with Jenkins and the Gitea Plugin for Jenkins.
Using a webhook for all events in the gitea organization and and organization folder on the Jenkins side.
The new status webhook (#27151) introduced in 1.23.0 has the X-GitHub-Event, X-Gitea-Event and X-Gogs-Event headers missing/empty:
Request URL: http://jenkins:8080/gitea-webhook/post
Request method: POST
Content-Type: application/json
X-GitHub-Delivery: e862f2f7-cf9e-4903-8f95-5c67f51ac3bc
X-GitHub-Event:
X-GitHub-Event-Type: status
X-Gitea-Delivery: e862f2f7-cf9e-4903-8f95-5c67f51ac3bc
X-Gitea-Event:
X-Gitea-Event-Type: status
X-Gitea-Signature:
X-Gogs-Delivery: e862f2f7-cf9e-4903-8f95-5c67f51ac3bc
X-Gogs-Event:
X-Gogs-Event-Type: status
X-Gogs-Signature:
X-Hub-Signature: sha1=
X-Hub-Signature-256: sha256=
push webhooks work for me as well. The issue currently only occurs with status webhooks (have tested push, create, pull_request and status webhooks with version 1.23.1). All except the status webhook have the headers set (with different values of course).
My workflow looks something like this:
sequenceDiagram
User->>Gitea: commit
Gitea->>Jenkins: push-webhook
Jenkins->>Gitea: status update: building
Gitea->>Jenkins: status-webhook
Note right of Jenkins: Here the error occurs because of the missing header
Loading
Based on that you will need something like this to trigger the status webhook without Jenkins:
Description
I am using Gitea in combination with Jenkins and the Gitea Plugin for Jenkins.
Using a webhook for all events in the gitea organization and and organization folder on the Jenkins side.
The new status webhook (#27151) introduced in 1.23.0 has the
X-GitHub-Event
,X-Gitea-Event
andX-Gogs-Event
headers missing/empty:In comparison a webhook for a push event:
Because of this the Jenkins plugin returns an error code with the log message:
I think this should be ultimately be made more robust in the plugin but is probably a bug here as well.
Gitea Version
1.23.1
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
2.47.1
Operating System
Debian 12
How are you running Gitea?
using
gitea/gitea:latest
docker imageDatabase
MySQL/MariaDB
The text was updated successfully, but these errors were encountered: