-
Notifications
You must be signed in to change notification settings - Fork 42
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
Does not work with jobs in folders #10
Comments
Tested this and I think you can just use "bar" as the job name in Gogs/Gitea, so: This also showed me a problem with the fact that we at the moment only look at the job.getName() . @jf647 could you confirm that only the job name is enough to get the stuff running? |
Think this can be closed since #12 is merged |
#12 is merged :-) |
@willemvd Yes, this works by just supplying the job name while using foldered jenkins setups. |
@sanderv32 When will this change released? Or how do I use nightly builds or something? |
@fuhbar You can get an SNAPSHOT artifact from the JenkinsCI buildserver for the time being. Will try to release a the new version before the end of the week. |
When using the Cloudbees Folder plugin, the webhook cannot start jobs that are in folders. The log reports:
WARNING: Job 'foo/bar' is not defined in Jenkins
Feb 19, 2017 10:00:19 PM org.jenkinsci.plugins.gogs.GogsWebHook exitWebHook
WARNING: Job 'foo/bar' is not defined in Jenkins
Feb 19, 2017 10:01:23 PM org.jenkinsci.plugins.gogs.GogsWebHook doIndex
WARNING: Job 'foo/job/bar' is not defined in Jenkins
Feb 19, 2017 10:01:23 PM org.jenkinsci.plugins.gogs.GogsWebHook exitWebHook
WARNING: Job 'foo/job/bar' is not defined in Jenkins
When I move this job to the root of my Jenkins server, it works properly.
In the webhook in gitea, I've tried using url-encoded and raw slashes to separate path elements with no observable change. I suspect gitea is encoding it for me in the later case. I've also tried putting 'job' as an element between the folder and the job, as this is what the Jenkins address bar shows, also without success.
The text was updated successfully, but these errors were encountered: