And I'd like to add:
If the first line of a shell build step starts with hashbang (#!),
then Jenkins will simply drop the script as is into a tmp file and
execute it.
Otherwise Jenkins copies the script into a tmp file and executes it
using /bin/sh -xe /tmp/somefilename
And /bin/sh, is just the
And you can shut up zip completelly with -qq
Garami Gábor
gabor.gar...@hron.me
Skype: hron84
Tel: +36 20 235 9621
Sent from my T-Mobile G2
Ezt a levelet telefonról adták fel, ékezethibákat tartalmazhat.
2012.04.11. 11:16, "David Aldrich" ezt írta:
> Hi
>
> ** **
>
> Some of my Jenkins jobs
Thanks for both answers,
David
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Zoltan Gyarmati
Sent: 11 April 2012 10:42
To: jenkinsci-users@googlegroups.com
Subject: Re: How to make a shell script quieter?
Hi,
it's more a bash question
Hi,
it's more a bash question than jenkins, but the point is, Jenkins calls
the bash with -x option enabled, which also prints the invoked commands,
with a "+" prefix
You can disable it with with the "set +x" command form your script, try
it with this snippet:
"""
Jenkins build steps call shell scripts with the option -x, this enables the
tracing of the shell script.
use "set +x" in your shell script or at the beginning of the build step
script to turn the tracing off again.
Normally the "noisiness" is very helpful to check if the build has done
properl