Provide a Jenkins plugin for gitea #674

@lunny commented on GitHub (Apr 28, 2017):

@martinellison It should be work since Gitea is forked from Gogs.

@lunny commented on GitHub (Apr 28, 2017): @martinellison It should be work since Gitea is forked from Gogs.

GiteaMirror commented

See https://github.com/jenkinsci/gogs-webhook-plugin/issues/6

@strk commented on GitHub (Apr 28, 2017):

@strk commented on GitHub (Apr 28, 2017): See https://github.com/jenkinsci/gogs-webhook-plugin/issues/6

GiteaMirror commented

@stephenc commented on GitHub (Jul 18, 2017):

Actually see https://github.com/jenkinsci/gitea-plugin

@stephenc commented on GitHub (Jul 18, 2017): Actually see https://github.com/jenkinsci/gitea-plugin

GiteaMirror commented

@vynshin commented on GitHub (May 20, 2018):

I had tried installing the gitea-plugin a couple times on a the latest jenkins build 2.107.3 but it doesn't seem to work.

@vynshin commented on GitHub (May 20, 2018): I had tried installing the gitea-plugin a couple times on a the latest jenkins build 2.107.3 but it doesn't seem to work.

GiteaMirror commented

@jalcine commented on GitHub (Aug 19, 2018):

Echoing what @gchung01 mentioned; the documentation on both the plugin page and the README of the plugin doesn't give much information on how to use it.

@jalcine commented on GitHub (Aug 19, 2018): Echoing what @gchung01 mentioned; the documentation on both the plugin page and the README of the plugin doesn't give much information on how to use it.

GiteaMirror commented

@bkahlerventer commented on GitHub (Sep 27, 2018):

Tried to use the plugin on gitea 1.5.1 It always gives Could not communicate with server: HTTP 403/Forbidden. Tried using gitea token. The plugin appears abandoned, last updates are 6 months ago, there is no way to contact the owner.

@bkahlerventer commented on GitHub (Sep 27, 2018): Tried to use the plugin on gitea 1.5.1 It always gives Could not communicate with server: HTTP 403/Forbidden. Tried using gitea token. The plugin appears abandoned, last updates are 6 months ago, there is no way to contact the owner.

GiteaMirror commented

@stephenc commented on GitHub (Sep 27, 2018):

Token does not work at present by design as the Jenkins git plugin doesn’t support redaction of the token from the logs. Just use user/pass

@stephenc commented on GitHub (Sep 27, 2018): Token does not work at present *by design* as the Jenkins git plugin doesn’t support redaction of the token from the logs. Just use user/pass

GiteaMirror commented

@stephenc commented on GitHub (Sep 27, 2018):

(I am waiting on gitea to expose tag details via rest api before I allocate my next time budget to this plugin... been waiting a while now and no progress yet https://github.com/go-gitea/gitea/issues/2738 if you have any influence)

@stephenc commented on GitHub (Sep 27, 2018): (I am waiting on gitea to expose tag details via rest api before I allocate my next time budget to this plugin... been waiting a while now and no progress yet https://github.com/go-gitea/gitea/issues/2738 if you have any influence)

GiteaMirror commented

@lafriks commented on GitHub (Sep 27, 2018):

@stephenc we are already feature freeze but I will implement it in next version

@lafriks commented on GitHub (Sep 27, 2018): @stephenc we are already feature freeze but I will implement it in next version

GiteaMirror commented

@stephenc commented on GitHub (Sep 27, 2018):

@lafriks totally fine... just ping me when #2738 is implements (or you have an easy to try prototype) and I'll schedule a slot to put some work in the plugin to consume the new api)

@stephenc commented on GitHub (Sep 27, 2018): @lafriks totally fine... just ping me when #2738 is implements (or you have an easy to try prototype) and I'll schedule a slot to put some work in the plugin to consume the new api)

GiteaMirror commented

@bkahlerventer commented on GitHub (Dec 5, 2018):

Token does not work at present by design as the Jenkins git plugin doesn’t support redaction of the token from the logs. Just use user/pass

@stephenc if I understand you correctly I should encode the user name and password with the URL in Jenkins config? I tried that but I still get "Could not communicate with server: HTTP 403/Forbidden".

Whether I turn on manage hooks and select a credential user with full admin rights on gitea, or supply userid:password or both, the gitea plugin always give me a 403/Forbidden message. I am running gitea on my local laptop and access it via http://localhost:3000

Update: Event tried ip address, http://127.0.0.1:3000 - no go.

@bkahlerventer commented on GitHub (Dec 5, 2018): > Token does not work at present _by design_ as the Jenkins git plugin doesn’t support redaction of the token from the logs. Just use user/pass @stephenc if I understand you correctly I should encode the user name and password with the URL in Jenkins config? I tried that but I still get "Could not communicate with server: HTTP 403/Forbidden". Whether I turn on manage hooks and select a credential user with full admin rights on gitea, or supply userid:password or both, the gitea plugin always give me a 403/Forbidden message. I am running gitea on my local laptop and access it via http://localhost:3000 Update: Event tried ip address, http://127.0.0.1:3000 - no go.

GiteaMirror commented

@stephenc commented on GitHub (Dec 5, 2018):

I should encode the user name and password with the URL in Jenkins config

No! Never

Just create a username password credential with your username and password and select that as the credentials.

@stephenc commented on GitHub (Dec 5, 2018): > I should encode the user name and password with the URL in Jenkins config No! Never Just create a username password credential with your username and *password* and select that as the credentials.

GiteaMirror commented

@bkahlerventer commented on GitHub (Dec 5, 2018):

@stephenc without turning on manage hooks, I cannot select credentials for the plugin to use

@bkahlerventer commented on GitHub (Dec 5, 2018): @stephenc without turning on manage hooks, I cannot select credentials for the plugin to use

GiteaMirror commented

@stephenc commented on GitHub (Dec 5, 2018):

You can... that's at the job configure page

@stephenc commented on GitHub (Dec 5, 2018): You can... that's at the job configure page

GiteaMirror commented

@stephenc commented on GitHub (Dec 5, 2018):

I'm uploading a video to youtube to show a quick walk through of set-up from scratch... give it a few minutes to encode

@stephenc commented on GitHub (Dec 5, 2018): I'm uploading a video to youtube to show a quick walk through of set-up from scratch... give it a few minutes to encode

GiteaMirror commented

@stephenc commented on GitHub (Dec 5, 2018):

Uploading is slow too... not just encoding!

@stephenc commented on GitHub (Dec 5, 2018): Uploading is slow too... not just encoding!

GiteaMirror commented

@bkahlerventer commented on GitHub (Dec 5, 2018):

no problem... :-)

@bkahlerventer commented on GitHub (Dec 5, 2018): no problem... :-)

GiteaMirror commented

@stephenc commented on GitHub (Dec 5, 2018):

At approx 9:06 in the video you will see the credentials drop down in an org folder. There are equivalent drop-downs in the other job types. There should be an Add button beside, but even if there isn't you can use the Jenkins credentials management screen to add the credential and it should show in the drop down.

@stephenc commented on GitHub (Dec 5, 2018): At approx 9:06 in the video you will see the credentials drop down in an org folder. There are equivalent drop-downs in the other job types. There should be an `Add` button beside, but even if there isn't you can use the Jenkins credentials management screen to add the credential and it should show in the drop down. <img width="1214" alt="screenshot 2018-12-05 at 11 04 35" src="https://user-images.githubusercontent.com/209336/49509615-ca187100-f87d-11e8-8b42-c45a34d3edfd.png">

GiteaMirror commented