to redirect the output to a file:
customer.script > app.log 2>&1
to redirect the output to nothing:
windows: customer.bat > NUL 2>&1
unix: customer.sh > /dev/null 2>&1
Ok, in our case (BLPackage Deploy Job) apparently whatever an External Command writes on STDOUT gets lost, while everything written to STDERR gets printed in the Job logs.
doesn't appear in logs, while
echo "RUNNING" 1>&2
does appear in the logs, as follows:
Warning Sep 10, 2009 3:53:14 PM stderr:%202 RUNNING
So apparently BLPackage Deploy Jobs are designed so that anything written by an External Command (STDOUT) doesn't appear in the logs, unless it's an error (STDERR), which is shown as a Warning.
the redirects should handle that afaik. redirect stdout to /dev/null and stderr to stdout should not send the messages to the console.
If you want to see the message, then just choose to show "All Information" as an option on the deploy job.
Many thanks. Will try