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
Classes with Same name and Different Packages are being triggered - AzureCredentials #963
Comments
This should be directed at the @jenkinsci/azure-devops-team 😅 They are the once who created the conflicting names. |
I hacked around it in a PR to this plugin and set a symbol: but yeah it's bad class design which is causing this problem, not related to JCASC, should create an issue on jira. |
@Ilhicas please feel free to open a ticket on Jira and I will follow up, thanks. |
@gavinfish |
#964 is somewhat related |
@gavinfish I've created issue with the same description as here. If you require any further info on how to reproduce, I'll be happy to provide https://issues.jenkins-ci.org/browse/JENKINS-58710 @oleg-nenashev yes the @ symbol isn't resolved, as I've used 1.1.0 for storage, that has the @ symbol @timja added, but without luck. |
[X ] Jenkins version 2.187
[X] Plugin version -configuration-as-code:1.24 && configuration-as-code-support:1.18
OS - Alpine (Docker Official Image)
Description
When using Azure Credentials with CASC references to Azure Credentials ( plugin azure-credentials:1.6.1 ) get caught by a different package
Example for CASC confs
This results in:
The same is valid if we set Azure Storage Credentials
The values for azureStorageAccount have been exported from CASC to check if setting it would not trigger this bug.
The above results in triggering twice the Same StackTrace as set above.
Notice the package used:
com.microsoftopentechnologies.windowsazurestorage.helper.AzureCredentials
It should in fact call the one below:
com.microsoft.azure.util.AzureCredentials
The text was updated successfully, but these errors were encountered: