From Stack Overflow
<https://stackoverflow.com/questions/26506539/reference-to-a-bash-variable-whose-name-contains-dot>:
depdir=`env|grep "deploy\\.dir="|cut -d = -f 2`
echo "deploy.dir == $depdir"
-Eric
On 2/8/2019 3:29 PM, Eric Fetzer wrote:
Sorry, no again:
/tmp/jenkins6366597011192684630.sh: line 2: ${params.'deploy.dir'}: bad
substitution
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]
<mailto:[email protected]>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/613d8387-e420-4898-b8da-47fbed8aeceb%40googlegroups.com
<https://groups.google.com/d/msgid/jenkinsci-users/613d8387-e420-4898-b8da-47fbed8aeceb%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.
--
Eric Pyle
Siemens PLM Software
Lebanon, NH
+1 603-277-3060
[email protected]
http://www.siemens.com/plm
--
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/b1d96288-8630-908c-b254-9beb6b18e0a7%40siemens.com.
For more options, visit https://groups.google.com/d/optout.
