-
Notifications
You must be signed in to change notification settings - Fork 39
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
Duplicate class definition for OwnershipGlobalVariableImpl #84
Comments
Looks like a valid bug, not sure whateher the Ownership Plugin is a root cause. I will try to investigate |
Did you have time to investigate the issue? Below is a more detailed error message:
|
This is a build pipeline that is able to produce the issue (not always, but for me nearly 50%):
|
Hi @gpxricky . My apologies, I forgot about this TODO item. Added it to my list . Looks like it is similar to of https://issues.jenkins.io/browse/JENKINS-48628 / https://issues.jenkins.io/browse/JENKINS-50171 , which are related to use of packages in global variables. jenkinsci/workflow-cps-plugin#214 from @abayer fixed a similar issue in |
Thanks, Oleg. Is there any workaround you can think of that I can access the information two times in my pipeline? Edited: the following code within my shared library seems to work fine:
|
Hi,
I'm using the plugin in a Declarative Pipeline. I access the job owners in two different stages, in a normal build stage and in the cleanup stage.
Unfortunately I now sometimes get the following error:
I don't think it has something to do with it, but the problem appeared only (?) after introducing the feature of sequential stages. However, the ownership plugin is only accessed within one of the two stages blocks.
Below you find the functions that I'm using in a custom step of my shared library. This code is accessed two times, in the normal stage and in the cleanup stage:
I'm using version
0.12.1
of the plugin.The text was updated successfully, but these errors were encountered: