Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-75661

Ambiguous release notes for latest release. How do I ensure this is done? "Make sure both tokenCache and tokenExpiryCache are initialized if needed"

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Blocker Blocker
    • hashicorp-vault-plugin
    • None

      We recently updated Jenkins from 2.462.2 to 2.492.3 with the latest plugins.  After the update, the Hashicorp Vault Username-Password Credentials types are no longer showing up in the credentials drop down for Organizational folders and multibranch folders.  Only local Jenkins credentials are shown.  

      The problem is that the vault username-password credential is missing from the credential drop down.  I believe this issue is from the cloudbees-bitbucket-branch-source plugin and have opened a ticket for that plugin here, https://issues.jenkins.io/browse/JENKINS-75659

      However, the latest version of the hashicorp-vault-plugin has a comment, "Make sure both tokenCache and tokenExpiryCache are initialized if needed".

      I followed the pull request notes but still don't understand what this means.

      Can you tell me how I can insure that tokenCache and tokenExpiryCache has been initialized?

      Is this in my hashivault configuration or Jenkins?

      Maybe the token cache initialization  is our core issue but until I can figure out what this means, it is a critical blocker for us and can no longer use the vault plugin.

            ptierno Peter Tierno
            bill_settle Bill
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: