-
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
Job 'dirname/jobname' is not defined in Jenkins #36
Comments
@urusha Investigating this problem. Can you confirm that version 1.0.11 is working? |
Yes, confirming. |
Thanks. Found the problem and i'm working on PR #37 which fixes the problem. Will release a new version of the plugin before or in the weekend. |
Released version 1.0.13 with the fix. Integration test is also inplace so if this breaks again it's noticed. |
Hello @sanderv32, even with your last Pull Request, i'm still facing that issue : Jenkins version : 2.110 I'm using a Multibranch pipeline called "application-streams" defined on Jenkins into a job with the same name and display name : application-streams. I'm using your plugin since a long time ago but the Webhook is still flaky and not fully functionnal : This is my webhook config on the Gogs's side, and here my Jenkins job : The Scan is going well but when i try to use the webhook by pushing or just by using the test request drectly on Gogs i still have : I thought that the last PR fixed that, do you have any ideas ? Thanks |
@theobolo Can you please paste the request part as its clear that the response shows the job can't be found. |
@sanderv32 Hello, there it is :
|
@sanderv32 Well it seems that not all my job are concerned about that... i've a Jenkins job called "docker-elasticsearch" on the same repo, but under the user I'm not sure where this come from but it's working with some jobs... And the working request :
|
@theobolo Just out of curiosity, did the previous version of the webhook-plugin show the same behaviour? |
@sanderv32 I'm not really sure about that, i know that it was working recently but still flaky, but i can't tell if i was on 1.0.12 or a previous one. Basically it's working on some jobs, even on job with the same |
@sanderv32 I found that the master branch is working on the |
@theobolo Thanks for the info. I will try to work on the plugin this weekend. |
@theobolo Just tested the plugin with the multibranch plugin but everything seems to be working fine. What does the multibranch scan log show? |
@sanderv32 Yep it's working with multibranch but not on all my branches, maybe because i usea kind of it's happening 99% on that kind of branches, the scan is correct and it founds all the branches. I created a |
Thanks for that info @theobolo . The refs are split by slash and the last element is used as the job name, but if the slash is part of the branch/tag name the split doesn't work correctly. Just made a new version and tested it against a branch with a slash and it worked. Will push the fix to another PR and if that one is building correctly I will create a new release. |
Released version 1.0.14 with the fix. Please let me know if this version works so we can close this issue. |
@sanderv32 Very well done ! It's working now :) Great Thanks You can close this issue 👍 |
@theobolo Have close this issue, but also want to thank you for pointing out this bug. |
With the last release I still get
{"result":"ERROR","message":"Job 'dirname/jobname' is not defined in Jenkins"}
if the job is placed in a folder. Without folder all is ok.The text was updated successfully, but these errors were encountered: