Hello! I have just started using both Gitea and Jenkins on a local Kubernetes node, but I have some problems with webhooks.
My current status is:
I have created a Gitea org in Jenkins, which is correctly seeing the various repositories, including the only one that has a Jenkinsfile; if I manually start builds on that repository, it works correctly
I have manually created a webhook in Gitea, which seems to be working since each request (whenever I commit to master) correctly sends a request and receives the answer âProcessedâ by Jenkins.
The problem is that nothing happens on Jenkins: there is no build being created at all. I have checked the various URLs (both in Jenkins config and in the webhook) to be sure that I was not using locahost or the wrong port, and so far it seems this is not the case. Am I missing some steps?
I can access the configuration for org/repository/master in Jenkins, the one with âBuild triggersâ, but everything is greyed out and I cannot select anything from there, so I cannot try stuff like âPoll SCMâ (which I donât know if it should be needed).
Yes I tried it Does not work ⌠in gitea I tested the webhook and the response is âprocessedâ ⌠In jenkins no build was automated triggered. In Jenkins I can start a build manually.
There are no log entries visible so I have no idea where the problem comes from.
The URL in the webhook has to be the same like the âROOT_URLâ entry in the app.ini of the gitea configuration file. I used in this entry not the ip address but the machine name.
Hi, could you give me the details on how you solved it? I still didnât understand by "the same like the ROOT_URL ". Currently, my gitea and docker are running on separate docker containers but are on the same network. Jenkins can access my gitea repos and gitea successfully sends request to the webhook and gets a 200 response with Processed.
My gitea webhook is set to âhttp://<Ip of the container>/gitea-webhook/postâ. I also tried setting it to âhttp://<ContainerName>/gitea-webhook/postâ. Both of these webhook urls get a 200 response but does not trigger build in my jenkins.