Odtnhj

I have a Jenkins server (v 2.138) running on a Windows 7. I also have cygwin installed. The cygwin path is in the windows path, so Jenkins jobs can call cygwin executable.

My question is: why in Build action, when I set an "Execute shell" action, the resulting call (confirmed by the build console output) is something like:

sh -xe C:WindowsTEMPjenkins8280072687577604153.sh

I understand the temp script being generated from what I enter in the jobs configuration. What I don't understand is the "-xe" arguments passed to the sh.

From what I see, these options seems to print internal commands output. Similar to echo ON in windows? However, this has the adverse effect of polluting our build logs.

For example:

Job configuration:

echo X > a.txt
echo X > b.txt
echo X > c.txt
grep X $( find -name "*.txt" )

Resulting log:

+ echo X
+ echo X
+ echo X
++ find -name '*.txt'
+ grep X ./a.txt ./b.txt ./c.txt
./a.txt:X
./b.txt:X
./c.txt:X

If possible I would only like to get:

./a.txt:X
./b.txt:X
./c.txt:X

On my machine, I get:

$ sh --version
GNU bash, version 4.4.12(3)-release (x86_64-unknown-cygwin)
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>

This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Therefore, I looked at the bash man page, but I cannot find any reference to -x or -e options.

Do you have any suggestion on how I could tell Jenkins to call the script directly, something like:

sh C:WindowsTEMPjenkins8280072687577604153.sh

Or if not possible, how I could inside my job, overwrite these settings to only print relevant console output, not anything intermediate.

Thanks!