Within the last two weeks, we I added a code signing certificate to Azure Key Vault and started using the Azure Key Vault plugin to download the certificate to sign a client application during the build process.
Twice now we've had a build break. Investigation both times led us me to the Manage Jenkins / Configure System page where we I found both fields for the Azure Key Vault Plugin were reset to blank.
After re-setting the Key Vault URL and Credential ID, the build succeeded.
There's only one person in our organization maintaining Jenkins' global configuration,: me.
I can't explain how these settings are getting blanked out, so I'm left to wonder if there is a defect in the plugin.
It's possible (likely) that we've upgraded Jenkins core recently, but I've never seen Jenkins lose global config on a core update.
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.