It IS adding the single quotes to build parameters!
On Friday, December 18, 2015 at 7:58:04 PM UTC-5, Daniel Beck wrote:
>
> I answered this on IRC. Here's basically the same answer again:
> http://stackoverflow.com/a/34364786
>
> On 18.12.2015, at 22:57, no...@gmx.com wrote:
>
> > I've also t
I answered this on IRC. Here's basically the same answer again:
http://stackoverflow.com/a/34364786
On 18.12.2015, at 22:57, no...@gmx.com wrote:
> I've also tried doing this:
> Name: OPTS
> Default Value: -o tmp -e "arg1=${VAR1} arg2=${VAR2} arg3=${VAR3}"
>
> Execute shell command:
> ARGS=$(ech
I've also tried doing this:
Name: OPTS
Default Value: -o tmp -e "arg1=${VAR1} arg2=${VAR2} arg3=${VAR3}"
Execute shell command:
ARGS=$(echo $OPTS)
./build_app $ARGS
Console Output:
++ echo -o tmp -e '"arg1=value1' arg2=value2 'arg3=value3"'
+ ARGS='-o tmp -e "arg1=${VAR1} arg2=${VAR2} arg3={VAR3
I basically have a string parameter that contains values from other parameter
fields, which I then use again in the Execute shell command.
However, Jenkins adds single quotes in erroneous places within that string,
which makes the executing application unable to parse the arguments.
Example:
