It won't work as of SECURITY-170. See https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-05-11 for details.
Can't you list all of those parameters with some left undefined depending on the build? Cheers Le 3 août 2016 8:54 PM, "Nick Grealy" <[email protected]> a écrit : > Ok, what happens when the parameter names are dynamic (ie. Not known in > advance)? > > Should I be using environment variables instead? (How do I add them > programmatically?) > > Thanks > > -- > 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/9274c1af-eaff-40b6-bb09-cefbb83fbbdf%40googlegroups.com > . > For more options, visit https://groups.google.com/d/optout. > -- 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/CANWgJS5yw0eLSvyFadurm1-pmOjtM-xKHhpLH%2BHWEYpnw-A01A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
