What makes Credential Parameter special that it can be used in Bind area?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

What makes Credential Parameter special that it can be used in Bind area?

Michael Carter
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/31918aae-5e4e-46c8-ae39-6e80363d37a3n%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: What makes Credential Parameter special that it can be used in Bind area?

Matt Sicker
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-builds

On Thu, Aug 20, 2020 at 4:29 PM Michael Carter
<[hidden email]> 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 [hidden email].
> 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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAEot4ozg_Bco2fZ51%3D3yeDE43wP_NXa6%3D7cPWVsBBHWcmZi3yA%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: What makes Credential Parameter special that it can be used in Bind area?

Matt Sicker
More info is in that doc elsewhere by the way such as the guide for
exposing said UI:
https://github.com/jenkinsci/credentials-plugin/blob/master/docs/consumer.adoc#providing-a-ui-form-element-to-let-a-user-select-credentials

On Fri, Aug 21, 2020 at 10:38 AM Matt Sicker <[hidden email]> wrote:

>
> 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-builds
>
> On Thu, Aug 20, 2020 at 4:29 PM Michael Carter
> <[hidden email]> 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 [hidden email].
> > 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



--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAEot4oxGE6vcSt93TTOekwv5F%2B9oPkvGOFnRY3yTvZG7zCJMow%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: What makes Credential Parameter special that it can be used in Bind area?

Michael Carter
Thanks that got me to where I needed to be.  my solution was a fresh class modelled after CredentialsParameterValue... didn't realize there was a step actually looking for the CredentialsParameterValue class.   So now I'm extending it and heavily overriding everything.  My solution is working now.

Thanks again.
Michael

On Friday, August 21, 2020 at 11:39:17 AM UTC-4 [hidden email] wrote:
More info is in that doc elsewhere by the way such as the guide for
exposing said UI:
https://github.com/jenkinsci/credentials-plugin/blob/master/docs/consumer.adoc#providing-a-ui-form-element-to-let-a-user-select-credentials

On Fri, Aug 21, 2020 at 10:38 AM Matt Sicker <[hidden email]> wrote:

>
> 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-builds
>
> On Thu, Aug 20, 2020 at 4:29 PM Michael Carter
> <[hidden email]> 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 [hidden email].
> > 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



--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/0bf1753f-bcac-4095-b565-6694d20fcd91n%40googlegroups.com.