Are you saying that it's not possible to make this work? The .'s are already in there. I guess I could write an ant script and just use them inside there because they work fine as parameters to a script...
On Friday, February 8, 2019 at 10:25:17 AM UTC-7, Eric Fetzer wrote: > > So it works fine to use a variable like build.dir as a parameter in a > build trigger. I'm finding, however, that when I add it to a "execute > shell" command, it gets cut off at the ".". For example: > > Execute Shell: > > Command: ls -l $deploy.dir > > This tries to ls -l on .dir because $deploy is unset. I would very much > appreciate any help. I tried escaping the "." but that didn't work. I > tried putting quotes around the variable, no help. Any help would be > greatly appreciated! > > Thanks, > Eric > -- 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/cf3db8bc-86be-43b2-a316-891976614704%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
