Hello Cyrille, thanks for your answer. The problem is, that the user has to activate the credentials binding plugin, select the credentials and a variable name, and insert the variable name as argument in the managed script each time he creates a new job. This is a little bit cumbersome. It would be great to have the functionality of Credentials Binding Plugin in Managed Files configuration, so that the user only has to chose the managed script, but not the credentials.
Jochen Am Montag, 23. Mai 2016 10:37:38 UTC+2 schrieb Cyrille Le Clerc: > > Hello Jochen, > > Did you look at the > https://wiki.jenkins-ci.org/display/JENKINS/Credentials+Binding+Plugin > and at the > https://wiki.jenkins-ci.org/display/JENKINS/Config+File+Provider+Plugin ? > > The former should let you use environment variables, the latter should let > you store the credentials in a file (cleaned up at the end of the build). I > think that the former makes more sense for your use case. > > Cyrille > > > On Monday, May 23, 2016 at 7:34:44 AM UTC+1, Jochen Fuerbacher wrote: >> >> Hello, >> >> I was wondering if it is possible to access the credentials of a user >> from managed files (e.g. parameters / variables). >> The managed file (Managed script file) needs to curl a url with a >> username:token combination and I don't want to hardcode this combination in >> the script. >> >> Thank you. >> > -- 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/72354ff3-c116-4f92-bd43-1cef1bf8556f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
