Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide a Jenkins plugin for gitea #1631

Closed
martinellison opened this issue Apr 28, 2017 · 22 comments
Closed

Provide a Jenkins plugin for gitea #1631

martinellison opened this issue Apr 28, 2017 · 22 comments
Labels
type/question Issue needs no code to be fixed, only a description on how to fix it yourself.

Comments

@martinellison
Copy link

Please provide a Jenkins plugin for gitea so that we can automate builds.

Note: there is a gogs plugin for Jenkins (does this work with gitea?).

@lunny
Copy link
Member

lunny commented Apr 28, 2017

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

@lunny lunny added the type/question Issue needs no code to be fixed, only a description on how to fix it yourself. label Apr 28, 2017
@strk
Copy link
Member

strk commented Apr 28, 2017 via email

@bkcsoft bkcsoft closed this as completed Apr 29, 2017
@stephenc
Copy link

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

@gchung01
Copy link

gchung01 commented 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.

@jalcine
Copy link

jalcine commented 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.

@bkahlerventer
Copy link

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.

@stephenc
Copy link

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
Copy link

(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 #2738 if you have any influence)

@lafriks
Copy link
Member

lafriks commented Sep 27, 2018

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

@stephenc
Copy link

@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)

@bkahlerventer
Copy link

bkahlerventer commented 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.

@stephenc
Copy link

stephenc commented 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.

@bkahlerventer
Copy link

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

@stephenc
Copy link

stephenc commented Dec 5, 2018

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

@stephenc
Copy link

stephenc commented 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
Copy link

stephenc commented Dec 5, 2018

Uploading is slow too... not just encoding!

@bkahlerventer
Copy link

no problem... :-)

@stephenc
Copy link

stephenc commented 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.

screenshot 2018-12-05 at 11 04 35

@stephenc
Copy link

stephenc commented Dec 5, 2018

https://youtu.be/B4boQozMaRA is claimed to be the video URL (now youtube is processing it)

@stephenc
Copy link

stephenc commented Dec 5, 2018

ok video is live. there is no audio!

@bkahlerventer
Copy link

great video, makes more sense now... please add to plugin docs sometime

@jalcine
Copy link

jalcine commented Dec 5, 2018

I appreciate you clarifying that @stephenc!

@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type/question Issue needs no code to be fixed, only a description on how to fix it yourself.
Projects
None yet
Development

No branches or pull requests

9 participants