title: gitea and jenkins webhook
body: <p>I am testing out Gitea and would like to it to trigger a Jenkins build, pretty basic use case.  I understand that there is the existing GOGs webhook pluging that can be used, but recently also found out that there is a Gitea plugin for Jenkins as well.</p>
  
  <p>In GOGS case you would call Jenkins via:
      <a href="http://localhost:8080/gogs-webhook/?job=job_name" rel="noreferrer">http://localhost:8080/gogs-webhook/?job=job_name</a></p>
  
  <p>In the example above, obviously updating the Jenkins location and job name as needed.</p>
  
  <p>The problem is there is no documentation for the Gitea plugin, but based on the source code, the URL should be:</p>
  
  <p><a href="http://jenkins-url/gitea-webhook/post" rel="noreferrer">http://jenkins-url/gitea-webhook/post</a></p>
  
  <p>The sequence I believe should happen is the following:</p>
  
  <ol>
  <li>Gitea sees the push activity and POSTs the info to Jenkins webhook</li>
  <li>Jenkins Gitea webhook sees the POST and uses the info to grab the new source code from Gitea.</li>
  </ol>
  
  <p>The question is how does the gitea plugin know what job to execute?  How do you specify this ?  Right now I can see that gitea is sending POST to Jenkins at the above URL but nothing is happening, the Jenkins logs also have no information to understand why its failing.</p>
  
  <p>EDIT:</p>
  
  <p>I am running into an issue here where after copying the generated public SSH key to the Gitea user account, Jenkins is still unable to access the repo in order to use Pipeline Editor.  Not sure what I'm missing here as I'm able to push/pull perfectly from localhost (outside of Docker environment) and have checked that the containers indeed can see each other perfectly as well....</p>
  
  <p>Thanks</p>