I printed the environment using a SET command (I'm using Windows). It shows
all the environment variables with spaces just fine. In fact, when I
created a batch script with references to the variables, %Virtual Machine
Name% for example, it evaluates correctly. This sounds more like a bug in
the Text File Operations plugin.
On Tuesday, October 16, 2018 at 6:56:10 PM UTC-4, t3knoid wrote:
>
> I can't seem to get access to the value of a variable with a space in its
> name. I am trying to use the Text File Operations plugin. I tried the
> following formats:
>
> VMName,${ENV,var="Virtual Machine Name"}
> VMName,${Virtual Machine Name}
>
> I can only get this to work if I use a variable without spaces and using
> the second format shown above (e.g. ${VirtualMachineName}. I prefer using
> the space because the Jenkins uses the variable name in the GUI as well.
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" 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-users/113b2c1f-b8d2-4709-95ba-c1caae40bebe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
