One option might be to use the token macro in a groovy script from the EnvInject (I believe it supports groovy scripts for setting variables). I don't know of any other way of doing it.
On Fri, Aug 22, 2014 at 12:07 PM, Paul Sokolovsky < [email protected]> wrote: > Hello, > > On Tue, 19 Aug 2014 08:40:35 -0700 > Slide <[email protected]> wrote: > > > I don't think that the token macro stuff should be integrated into the > > core. There are other ways of generating parameter values to pass > > along, I believe the EnvInject plugin is the way to go. Integrating > > Token Macro into core is not going to happen. > > So, I tried EnvInject plugin and didn't see it able to expand macros > like "${SCRIPTLER, scriptId="superscript.groovy"}" (they go literally). > Looking at > https://wiki.jenkins-ci.org/display/JENKINS/EnvInject+Plugin , > TokenMacro plugin is not listed in dependencies. I also grepped thru > EnvInject source code and don't see code sequences required to expand > code macros, as specified on > https://wiki.jenkins-ci.org/display/JENKINS/Token+Macro+Plugin page. > > [] > > -- > Best Regards, > Paul > > Linaro.org | Open source software for ARM SoCs > Follow Linaro: http://www.facebook.com/pages/Linaro > http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog > -- Website: http://earl-of-code.com -- 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]. For more options, visit https://groups.google.com/d/optout.
