* When deploying a new Jenkins instance for an existing project, any encrypted credentials are lost and/or unreadable. We believe the underlying cause is that the new Jenkins instance installs Jenkins with a new, randomly generated encryption key instead of re-using the existing key. We routinely bring up Jenkins instances by mounting an EBS volume with existing Jenkins data. Somehow the way we are bringing up the new Jenkins is causing it to generate a new encryption key that makes all our existing credential keys unreadable and we have to go fix the manually.
Is there a way to tell Jenkins to skip this step? Thanks, Stanford S. Guillory Southwest Airlines Co. Solutions Architect, APT -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/D582823D.2F072%25stanford.guillory%40gmail.com. For more options, visit https://groups.google.com/d/optout.
