As long as the UI in question is calling
CredentialsProvider.findCredentialsById(), that will automatically
parse the ${} syntax and replace them with parameter values. At a
super low level, this works via the following invisible action
attached to the build:
https://github.com/jenkinsci/credentials-plugin/blob/master/docs/consumer.adoc#binding-user-supplied-credentials-parameters-to-buildsOn Thu, Aug 20, 2020 at 4:29 PM Michael Carter <[email protected]> wrote: > > Was designing my own "Credential Parameter" (basically a clone of the > existing one with some extra on screen filtering) and it wasn't working... > kept getting: > > ERROR: Could not find credentials entry with ID '${Testing}' > > In trying to trace the problem... if I use a String parameter. I get the > same error. So my question what makes the "Credential Parameter" special > that you can use it's ${name} in the freestyle jobs Bind area for pulling > passwords to variables? > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" 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-dev/31918aae-5e4e-46c8-ae39-6e80363d37a3n%40googlegroups.com. -- Matt Sicker Senior Software Engineer, CloudBees -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" 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-dev/CAEot4ozg_Bco2fZ51%3D3yeDE43wP_NXa6%3D7cPWVsBBHWcmZi3yA%40mail.gmail.com.
