Hi, I have a parameterized job that takes a secret as parameter (specifically an Ansible vault password). This secret is so secret that I would like Jenkins to not persist it on disk.
My basic solution was to use a password parameters in a parameterized build, but they get stored (not in plaintext, but still) in build.xml in the job's history. Binding a credential to the job does not fit the bill either, as the credential itself will be stored in credentials.xml. Is there a way to pass a secret without seeing it persisted ? Some plugin maybe ? This could be done with a "unpersisted password" parameter type, but I don't know if that's possible (or has been implemented by anyone). I'm using Jenkins v1.642.3. Regards, Mathieu Garstecki -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/023428d7-ebf7-4af5-ae98-eb87209f5d06%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
