On Mon, Oct 21, 2019 at 11:00 AM Slide wrote:
> Token Macro will also work in pipeline jobs
Perhaps, but I would not recommend it.
https://jenkins.io/doc/developer/plugin-development/pipeline-integration/#variable-substitutions
--
You received this message because you are subscribed to the Goo
Thanks Gavin,
On Monday, October 21, 2019 at 6:00:24 PM UTC+3, slide wrote:
>
> Token Macro will also work in pipeline jobs and does provide some
> additional benefit in that you can have code behind the macro that does
> some stuff for you that you would have to do manually (and possibly throug
Thanks a lot, Will try that...
On Monday, October 21, 2019 at 6:00:24 PM UTC+3, slide wrote:
>
> Token Macro will also work in pipeline jobs and does provide some
> additional benefit in that you can have code behind the macro that does
> some stuff for you that you would have to do manually (an
Token Macro will also work in pipeline jobs and does provide some
additional benefit in that you can have code behind the macro that does
some stuff for you that you would have to do manually (and possibly through
either @NonCps or shared library). For something simple like a single
parameter or en
For something like a freestyle plugin, I think you need to use the token
macro plugin - https://wiki.jenkins.io/display/JENKINS/Token+Macro+Plugin
for pipeline, groovy will process the string before it gets to your code
On Mon, Oct 21, 2019 at 12:30 AM Tal Yanai wrote:
> Hi,
>
> Suppose I have m
Hi,
Suppose I have made a plugin implementation (a step) that asks the user for
a location (path) to a file on the disk.
When the user supply the value (using the job's configuration) he is using
Jenkins variables/params such as ${JOB_NAME} as part of the path he supply.
So for example, an inp
