jenkinsci-users@googlegroups.com
Betreff: Re: Return value of a command in shell script != 0 stops build
Or you can turn off error checking for a specific command by doing:
set +e
command
set -e
Andy.
On 14 August 2012 17:45, Sami Tikka < sjti...@gmail.com > wrote:
If you begin the b
Or you can turn off error checking for a specific command by doing:
set +e
command
set -e
Andy.
On 14 August 2012 17:45, Sami Tikka wrote:
> If you begin the build step with a line that starts with #!, Jenkins will
> assume you want to specify the interpreter instead of using /bin/sh -xe,
> wh
Add in a test to see if the director exists before doing the copy:
for P in /usr/contrib/bin /usr/local/bin
do
[ -d $P ] || continue
cd $P > /dev/null 2>&1
if [ $? -eq 0 ]
then
// XYZ
echo $P
fi
done
This will skip the iteration an
If you begin the build step with a line that starts with #!, Jenkins will
assume you want to specify the interpreter instead of using /bin/sh -xe, which
is the default. It is the -e switch of the shell which is responsible for
aborting the script when a command exits with error.
You could plac
Hi there,
I'm using Jenkins to build a C++ project on Solaris 10.
To set up the environment I'm calling various shell scripts, of which one
contains the following code:
--
for P in /usr/contrib/bin /usr/local/bin
do
cd $P > /dev/null 2>&1
if [ $? -eq 0 ]
then
