gt; reliably for all relevant jobs:
>
> https://cloudbees.zendesk.com/hc/en-us/articles/203802500-Injecting-Secrets-into-Jenkins-Build-Jobs
> If you have several people working on build jobs/scripts I would
> discourage from doing this.
>
> Am Sonntag, 24. April 2016 16:33:22 UTC+2 schrieb Da
For regular jobs if I don't want to make passwords publicly visible I use
EnvInject plugin with either global or job passwords.
This masks the passwords in log output and make them available as env
variables.
What is the right way to do this when wrting pipeline DSL scripts?
Thanks a lot!!!
--
