You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What Operating System are you using (both controller, and any agents involved in the problem)?
All is OpenShift and docker image based. We don't think there is something related to the issue here.
Reproduction steps
Create a global credentials with id IZ_USER at Jenkins root level
Create an Azure keyvault global credentials with id IZ_USER
Create a folder inside Jenkins (here called vivien in screenshots)
Create a pipeline inside folder using Git and try to retrieve the right IZ_USER credential
Expected Results
According to inheritance, credentials at folder level should be resolved instead of the Azure global ones.
We can see in the folder credentials inheritance is properly displayed
Actual Results
The wrong credentials are displayed in pipeline definition and is wrongly used at pipeline execution
Anything else?
No response
Are you interested in contributing a fix?
Yes. What we're missing is how the credentials priorities are computed / resolved in interaction with Azure KeyVault plugin
The text was updated successfully, but these errors were encountered:
to make sure to reproduce, you must declare 3 credentials with the same ID but with the 3 providers:
one global in Jenkins at root level (put username "test-jenkins")
one global with Azure plugin (at root level) (put username "test-azure")
one global at folder level (put username "test-folder")
In theory, the one at folder level should take precedence over the global ones at root level. When checking at my 1st screenshot and looking at "stores from parent", we see that Folder > Azure > System, so the resolved one should be the folder one (this is what we expect).
Create a Pipeline into that folder with the following definition:
Uh oh!
There was an error while loading. Please reload this page.
Jenkins and plugins versions report
What Operating System are you using (both controller, and any agents involved in the problem)?
All is OpenShift and docker image based. We don't think there is something related to the issue here.
Reproduction steps
Expected Results
According to inheritance, credentials at folder level should be resolved instead of the Azure global ones.
We can see in the folder credentials inheritance is properly displayed
Actual Results
The wrong credentials are displayed in pipeline definition and is wrongly used at pipeline execution
Anything else?
No response
Are you interested in contributing a fix?
Yes. What we're missing is how the credentials priorities are computed / resolved in interaction with Azure KeyVault plugin
The text was updated successfully, but these errors were encountered: