-
Notifications
You must be signed in to change notification settings - Fork 85
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
Plugin conflicting with global library configuration when configured with JCasC #319
Comments
How i can reproduce it locally? |
Hey @KostyaSha Thanks for getting back to me. Steps for reproducing:
As soon as you install the github integration plugin the above errors will throw. I have tried doing it the reverse order as well, installing the plugin first and then setting the configuration for the global library and it throws the same errors above. |
Btw, do you have |
Yup. These are all the git/github plugins I've got installed
|
This line is the problem: Line 336 in fbb6442
There is a name conflict, since there are multiple SCM sources named "github". A simple way to fix the problem is to rename the SCM source to "githubPullrequest" or similar, to use the same name as the plugin that provides it. |
I am having the same issue, both via JCasC and via GUI. You just need to have at least a global library defined in your Jenkins System settings and after that you install the GitHub Integration plugin, you will see in the logs the error reported originally by @efernandes-dev-ops @KostyaSha Any update about this issue? @johanblumenberg Thanks for your investigation! Did you suggest a solution for the plugin's developer or for the issue's reporter? I didn't get it. |
@vittoriocanilli I meant it as a solution for the plugin developer. But you could fork this plugin and fix it, and use your own version of the plugin. |
We seemed to have noticed an issue with the plugin. It seems to conflict with the global library configuration when it is configured via jenkins configuration as code. We get back the following errors:
Any ideas why would be helpful. Thanks
The text was updated successfully, but these errors were encountered: